Redshift Serverless namespaces should not use the default database name¶

This control checks whether an Amazon Redshift Serverless namespace uses the default database name, dev. The control fails if the Redshift Serverless namespace uses the default database name, dev.

How to fix¶

Attribute db_name of aws_redshiftserverless_namespace must be non-empty.

Implementation options¶

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Terraform AWS provider resources¶

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_redshiftserverless_namespace.

resource "aws_redshiftserverless_namespace" "this" {
  admin_username = "rsadmin"
  db_name        = "mydb"
  log_exports    = ["connectionlog", "userlog"]
  namespace_name = "pofix-example-namespace"
}

Which option should I choose?

Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings¶

Use these identifiers to cross-reference this control across tools, reports, and evidence.

Compliance.tf (CTF) Control: redshiftserverless_namespace_no_default_database_username
AWS Config Managed Rule: REDSHIFT_SERVERLESS_DEFAULT_DB_NAME_CHECK
Powerpipe Control: aws_compliance.control.redshiftserverless_namespace_no_default_database_username