Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifying Encryption for aws_s3_bucket_object #3475

Closed
ghost opened this issue Oct 10, 2015 · 7 comments
Closed

Specifying Encryption for aws_s3_bucket_object #3475

ghost opened this issue Oct 10, 2015 · 7 comments

Comments

@ghost
Copy link

ghost commented Oct 10, 2015

Is there a way that encryption can be specified for aws_s3_bucket_object?

@radeksimko
Copy link
Member

Sorry I misread your original issue, this is not quite supported yet for the aws_s3_bucket_object itself.
Keeping open.

@radeksimko
Copy link
Member

KMS encryption support was merged as part of #5453 and will be in the next release.

I'm keeping this open though, since encryption with customer key isn't supported yet.

@jason-riddle
Copy link
Contributor

jason-riddle commented Dec 11, 2016

So that lets you specify a KMS encryption key, but what about the AWS managed "AES256" option?

@conorgil
Copy link

@st-isidore-de-seville According to the aws_s3_bucket_object docs, this capability is now supported. If you agree, perhaps you can close this issue?

@radeksimko
Copy link
Member

@conorgil Thanks for the ping, but we don't actually support SSE via customer provided keys yet. The related attributes seem to be SSECustomerAlgorithm, SSECustomerKey and SSECustomerKeyMD5 which we don't use anywhere (yet).

Contributions are welcomed.

@conorgil
Copy link

conorgil commented May 1, 2017

@radeksimko Ah, ok. The initial issue description didn't clarify what was included feature wise and I didn't read your comment carefully until just now. Thanks for clarifying.

I am just learning go, so it might be a while before I can contribute on that level, but I'll take a crack at it down the road once I'm up to speed if no one gets to it first.

@github-actions
Copy link
Contributor

github-actions bot commented Jun 3, 2021

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants