Manual deletion of S3 bucket CORS does not force terraform to update CORS for bucket.

[jessegonzalez]

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 "me too" comments, 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 Version

Terraform v0.11.7
+ provider.aws v1.23.0

Affected Resource(s)

• aws_s3_bucket

Terraform Configuration Files

provider "aws" {
  region  = "us-east-1"
  version = " ~> 1.23.0"
  profile = "dev"
}

resource "aws_s3_bucket" "cors-testing-terraform" {
  bucket = "cors-testing-terraform"

  cors_rule {
    allowed_origins = ["some.fqdn", "another.fqdn"]
    allowed_methods = ["GET"]
    allowed_headers = ["*"]
    max_age_seconds = 3000
  }
}

Debug Output

Panic Output

Expected Behavior

After having deleted CORS configuration for an S3 bucket in the AWS console, terraform plan/apply should recognize the change and apply CORS configuration as defined.

Actual Behavior

CORS is left unconfigured.

Steps to Reproduce

1. terraform apply
2. Update S3 bucket and delete CORS configuration
3. terraform apply

Important Factoids

Other changes to the CORS configuration via console , i.e. adding AllowedOrigin or AllowHeader attributes are recognized and adjusted.

References

• None

[jessegonzalez]

I've created a PR for this issue: #4887

[bflad]

The fix for this has been merged into master and will release with version 1.24.0 of the AWS provider, very shortly.

[bflad]

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

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!