Using aws_s3_bucket_object with kms_key_id causes "etag" issues

[akarnani]

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

0.6.16

Affected Resource(s)

• aws_s3_bucket_object

Terraform Configuration Files

resource "aws_s3_bucket_object" "foo" { content = "abc" key = "foo" bucket = "${aws_s3_bucket.bar.id}" kms_key_id = "${aws_kms_key.main.arn}" }

Expected Behavior

On successive applies in which the content changes, they should be applied correctly

Actual Behavior

terraform appears to attempt to use an internally stored etag, however the check which prevents use of both etag and kms_key_id appears to fire and prevent the apply with the error message
aws_s3_bucket_object.foo: Unable to specify 'kms_key_id' and 'etag' together because 'etag' wouldn't equal the MD5 digest of the raw object data

Steps to Reproduce

1. terraform apply
2. alter content
3. terraform apply

[coen-hyde]

Yep, I just experienced this

[coen-hyde]

This only happens on update. The first creation of the s3 object works fine. Looks like etag is being set in the statefile after creation regardless of kms. See:

terraform/builtin/providers/aws/resource_aws_s3_bucket_object.go

Line 168 in 76b3c74

d.Set("etag", strings.Trim(*resp.ETag, `"`))

[luhn]

I'm also having a problem with this. Current workaround is to taint the resource.

[rvangraan]

Having the same problem. This only started happening when we upgraded to 0.7.2 from 0.6.x

[joseph-wortmann]

I am having the same problem after upgrading to 0.7.2

[catsby]

Hello friends – I just merged #9168, which adds an explicit conflict between etag and kms_key_id. You'll need to remove your etag if you're using kms_key_id. Sorry for the trouble!

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