Terraform-provider-aws: aws_s3_bucket force_destroy option has no effect on pre-existing bucket

[hashibot]

_This issue was originally opened by @jhoblitt as hashicorp/terraform#10738. It was migrated here as part of the provider split. The original body of the issue is below._

---

Terraform Version

$ ./bin/terraform --version
Terraform v0.8.0

Affected Resource(s)

• aws_s3_bucket

Terraform Configuration Files

resource "aws_s3_bucket" "ssh_public_keys" {
  region = "${var.aws_default_region}"
  bucket = "${var.bastion_bucket_name}"
  acl    = "private"
  force_destroy = true
  policy = <<EOF
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "1",
      "Effect": "Allow",
      "Principal": "*",
      "Action": [
        "s3:List*",
        "s3:Get*"
      ],
      "Resource": "arn:aws:s3:::${var.bastion_bucket_name}"
    }
  ]
}
EOF
}

Expected Behavior

bucket is deleted then recreated to modify IAM profile

Actual Behavior

$ ./bin/terraform import aws_s3_bucket.ssh_public_keys jhoblitt-bastion-test
aws_s3_bucket.ssh_public_keys: Importing from ID "jhoblitt-bastion-test"...
aws_s3_bucket.ssh_public_keys: Import complete!
  Imported aws_s3_bucket (ID: jhoblitt-bastion-test)
aws_s3_bucket.ssh_public_keys: Refreshing state... (ID: jhoblitt-bastion-test)
$ ./bin/terraform apply
...
aws_s3_bucket.ssh_public_keys: Modifying...
  force_destroy: "false" => "true"
aws_s3_bucket.ssh_public_keys: Modifications complete
Error applying plan:

1 error(s) occurred:

* aws_s3_bucket.s3_public_keys: Error deleting S3 Bucket: BucketNotEmpty: The bucket you tried to delete is not empty
    status code: 409, request id: 3991CB0128E5871C

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Steps to Reproduce

1. import an existing bucket
2. terraform apply

[wkentdag]

Any progress on a fix here? Experiencing the same issue.

~ terraform --version
Terraform v0.11.7
+ provider.archive v1.0.3
+ provider.aws v1.19.0

[b0ric]

Yep, facing exactly the same issue, please advise.

$ terraform --version
Terraform v0.11.7
+ provider.aws v1.29.0
+ provider.template v1.0.0

[snemetz]

I've seen this same issue on S3 buckets that Terraform created

[scsarver]

I have found this issue also. My case is specifically for s3 remote state assets. When I created the s3 buckets (remote state and logging) initially I saved the local state file. Simulating how to handle those remote state assets ephemerally I imported all my remote state assets into a new state file when I run a plan against that new state file both properties 'acl' and 'force_destroy' both are empty in the state file.

[willtrking]

Also ran into this issue. In my case I had a terraform destroy that error'ed before the bucket was destroyed, and now force_destroy has no effect.

[shashanksurya]

+1 Issue

[b-dean]

a hacky workaround is to just add

"force_destroy": "true"

to the attributes of the aws_s3_bucket resource in your tfstate. Then you can destroy it

[et304383]

If anyone comes across this, you have to do an apply first, then a destroy. You can't just add it to the tf file resource then run destroy.

[fahran]

Can confirm this is still an issue with Terraform v0.11.11, using aws provider v1.56.0.
In our case, the bucket was originally created with terraform, without force_destory=true set.

[navi86]

still issue, even if the bucket was previously created with force_destory=true set, but then removed from state and then added again.
the only workaround I see it's to set force_destroy manually

[GGAbhishek]

C:\UsersXXXXXX\AppData\Roaming\terraform.d>terraform --version
Terraform v0.12.29

• provider.aws v2.70.0

• tags = {
  - "Environment" = "Dev"
  - "Force_destroy" = "true"
  - "Name" = "Terraform bucket"
  } -> null

aws_s3_bucket.A: Destroying... [id=terraform-tf-test-bucket]

Error: error deleting S3 Bucket (terraform-tf-test-bucket): BucketNotEmpty: The bucket you tried to delete is not empty
status code: 409, request id: BF1A2439648F57A9, host id: UCpjN3HdIvzkjP4k/lSobOjy98+aQYZHiR/GPQ0bL92/jFnKyXEl00onXpUZJj+Yi8ApSZnBpng=

Force Destroy has no effect and cannot delete s3 bucket which has some content in it.