Closed JoshVCorp closed 1 week ago
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform Configuration Files
Relevant Variables:
variable "kms_key_id" { type = string description = "The ARN for the KMS encryption key." }
Debug Output
Panic Output
Expected Behavior
The aws_s3_bucket resource should be spun up without the AWS config rule (the managed rule here: https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-server-side-encryption-enabled.html) saying the S3 bucket is not in compliance.
Actual Behavior
The config rule linked above is alerting that our aws_s3_bucket resource is out of compliance. I think this is the result of the aws_s3_bucket resource itself and the aws_s3_bucket_server_side_encryption_configuration resource being 2 separate resources.
Steps to Reproduce
terraform apply
Important Factoids
References
Managed Config Rule: https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-server-side-encryption-enabled.html