-
Notifications
You must be signed in to change notification settings - Fork 25k
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
WIP: S3 client encryption #30513
WIP: S3 client encryption #30513
Conversation
Hi @gianrubio, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile? |
9d1fe2f
to
4ab9770
Compare
Pinging @elastic/es-distributed |
4ab9770
to
4513bd1
Compare
Thanks @gianrubio for this contribution. Adding client side encryption is a feature that is regularly requested, and the AWS SDK Java library provides everything to do it. I'm just concerned about few things:
|
Ok, I can wait until it got merged
Ok, same as above
It'll probably break the state because the restore action will try to decrypt files that are not decrypted. Any ideas on how can we avoid users to activate/desactivate in a existing repository? |
@gianrubio now that #30723 is merged, would you like to pick this PR up again? I think we should start by assuming that this setting is not dynamically enabled / disabled on a repo. |
@gianrubio Are you still planning to work on this? |
@albertzaharovits all yours |
This PR is a replacement of #16843 that was merged and later rolled back.
Before I wrote the docs I'd like to receive feedbacks about the changes.
Related to #11128
How to test?
Create Index
Load shakespeare example data
Create s3 repo
Create snapshot
List snapshots
Delete index
Restore snapshot