aws_iam_policy_document on S3 bucket attempts to destroy the bucket

[btilford]

Terraform Version

0.9.11

Expected Behavior

S3 bucket policy is updated without having to destroy the bucket.

Actual Behavior

• aws_s3_bucket.my-bucket: Error deleting S3 Bucket: BucketNotEmpty: The bucket you tried to delete is not empty. You must delete all versions in the bucket.
  status code: 409, request id: 123ABC "my-bucket"
• aws_s3_bucket.my-bucket: Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
  status code: 409, request id: 1234XYZ

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Create (terraform apply) an S3 bucket with an aws_iam_policy_document. I have multiple statements. 2 for internal network users to access the bucket and objects and then 2 more for specific users and roles to do the same.
2. Add an object to the bucket.
3. Modify the principal list for the policy.
4. terraform plan shows resources to create
5. terraform apply tries to delete the bucket and fails because there are objects in it.

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• Terraform aws s3 bucket policy are planned for change every time #4948
• provider/aws: Add aws_s3_bucket_policy resource #8615

[hashibot]

This issue has been automatically migrated to hashicorp/terraform-provider-aws#1326 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

[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 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.