Redshift Serverless namespaces should export logs to CloudWatch Logs¶

This control checks whether an Amazon Redshift Serverless namespace is configured to export connection and user logs to Amazon CloudWatch Logs. The control fails if the Redshift Serverless namespace isn't configured to export the logs to CloudWatch Logs.

How to fix¶

Attribute log_exports 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_export_connection_and_user_log_to_cloudwatch
AWS Config Managed Rule: REDSHIFT_SERVERLESS_PUBLISH_LOGS_TO_CLOUDWATCH
Powerpipe Control: aws_compliance.control.redshiftserverless_namespace_export_connection_and_user_log_to_cloudwatch