Error updating S3 Bucket tags: error setting resource tags: NoSuchBucket: The specified bucket does not exist

[bpiper]

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 Version

0.10.8

Affected Resource(s)

• aws_s3_bucket

Terraform Configuration Files

resource "aws_s3_bucket" "mybucket" {
  bucket = "mybucket"
  force_destroy = true

  lifecycle {
    prevent_destroy = false
  }

  tags = {
    Name = "mybucket"
    Role = "whatever"
  }
}

Expected Behavior

New S3 bucket created and tagged successfully.

Actual Behavior

Bucket was created from Terraform's perspective, but tagging failed with following error due to eventual consistency.

aws_s3_bucket.mybucket: error updating S3 Bucket (mybucket) tags: error setting resource tags (mybucket): NoSuchBucket: The specified bucket does not exist

Steps to Reproduce

Bucket resource must not exist yet. Run terraform apply (see example resource definition above). May need to destroy and apply a number of times before hitting the error (which by its nature doesn't always occur). I've been hitting this error quite a lot recently.

References

• Very similar to Error creating S3 bucket with tags - error getting S3 bucket tags: NoSuchBucket: The specified bucket does not exist  #10068 - which pertained to retrieving tags rather than updating them

[ewbankkit]

Similar:

• aws_s3_bucket_object eventual consistency error after object creation #12652

[dude0001]

Has anyone found a workaround or root cause for this?

[nomeelnoj]

We just hit this today as well with terraform 0.12.24. Any updates/workarounds at this time?

[boiaanstoianov]

Same error on v0.12.26 any updates on this issue ?

[github-actions]

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!

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