Redshift Cluster not fully setup when logging enabled

[rgn]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.10
hashicorp/aws v3.65.0 (self-signed, key ID 34365D9472D7468F)

Affected Resource(s)

• aws_redshift_cluster

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

main.tf

resource "aws_security_group" "bg_sg_edwh" {
  #tfsec:ignore:AWS009
  #tfsec:ignore:AWS007
  name        = join("-", ["security-group-edwh", var.environment])
  description = "Allow traffic to edwh services."
  vpc_id      = var.vpc_id

  egress {

    description = "Public communication."
    from_port   = 0
    to_port     = 0
    protocol    = "-1"
    cidr_blocks = ["0.0.0.0/0"] #tfsec:ignore:AWS009
  }

  tags = {
    Name        = join("-", ["security-group-edwh", var.environment])
    Environment = var.environment
  }
}

resource "aws_redshift_cluster" "bg_poc_rs_main" {
  cluster_identifier        = join("", [var.redshift_cluster_name, var.environment])
  database_name             = var.redshift_db
  master_username           = var.redshift_username
  master_password           = var.redshift_userpassword
  node_type                 = var.redshift_node_type
  cluster_type              = var.redshift_cluster_type
  cluster_subnet_group_name = aws_redshift_subnet_group.bg_rs_sg_group_main.name
  vpc_security_group_ids    = [aws_security_group.bg_sg_edwh.id]
  skip_final_snapshot       = true

  iam_roles = [aws_iam_role.bg_poc_iam_role_spectrum.arn]   
  cluster_parameter_group_name = aws_redshift_parameter_group.bg_poc_rs_main.id

  encrypted  = true
  kms_key_id = var.kms

  logging {
    enable        = "true"
    bucket_name   = join("-", ["log", var.environment, data.aws_caller_identity.current.account_id])
    s3_key_prefix = "redshift/"
  }

  tags = {
    Name        = "redshift cluster"
    Environment = var.environment
  }
}

Debug Output

Expected Behavior

Deploy the redshift cluster in one step.

Actual Behavior

Throws error while setting up logging, because cluster is yet not ready. Have to re-run terraform apply to get it running.

Steps to Reproduce

1. terraform apply

Important Factoids

Not that I'm aware of.

References

None

• #0000

[github-actions]

This functionality has been released in v3.69.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.