-
Notifications
You must be signed in to change notification settings - Fork 853
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
Client-Side Encryption #34
Comments
Any update on this feature? |
Not yet, unfortunately. It's definitely on our radar, but we're still trying to figure out when the right time is to tackle it. We know it's going to be a hard blocker for some people to migrate to V2. Can we assume that's the case for you as well? |
Yes, client-site encryption (or rather lack of) is a blocking issue from migration to this SDK version. |
I can see that it is possible to use client side encryption through PutObjectRequest from v1. Is that the target or just a temporary solution? |
Any news regarding ETA of this feature? |
@israelst11 Sorry, nothing to report at this time. |
Any updates? |
*bump |
Sorry, once we have something to report, we will update this issue. Feel free to +1 the related issue here, as well: aws/aws-encryption-sdk-java#58 |
We have started work on this issue but do not yet have a release date. |
@cenedhryn We are using Quarkus as our microservice framework and using aws sdk version v1 to decrypt the data from DynamoDB and running into issues while running the quarkus app. Any idea when the DynamoDB Encryption Client will be ready for aws sdk version v2? Thanks! |
When implementing the V2 encryption client, can we consider forwarding |
Any update on this issue? |
Looking for this feature. Want to try client side encryption with S3AsyncClient (AWS SDK 2.17.1). Currently using AmazonS3EncryptionV2.. from SDK 1.11.9 |
+1. Amazon Athena's only option for CSE is via the v1 AmazonS3EncryptionClient |
Please! We recently embarked on an SDK migration, but got stymied by lack of S3 client-side encryption and had to roll it all back. |
@wheezil thanks for the feedback. We're actively working on S3 client side encryption and are nearing completion. We'll comment on this issue when it's released. |
This is actually the only reason I need to use the sdk, just chiming in here that it's needed :) |
The AWS crypto tools team has launched the S3 encryption client with support for the AWS SDK for Java 2.x! https://docs.aws.amazon.com/amazon-s3-encryption-client/latest/developerguide/what-is-s3-encryption-client.html There's more in the works, but check it out and cut them some issues for anything you'd like to see! |
The new AWS Database Encryption SDK is out, in developer preview mode. As a reminder, libraries under |
The AWS Database Encryption SDK is now GA, so I'm closing this issue. Both new S3 Encryption and Database Encryption clients are independent libraries maintained by the AWS Crypto Tools team. To contact the maintainers, please open an issue in the respective Github repo:
|
|
Client-side encryption and signing is supported by
the S3 anddynamo DB clients in 1.11.x, but not in 2.0.x. This feature is used by a large number of customers and should be supported in 2.0.x.4/6/23 Update: The AWS crypto tools team has launched the S3 encryption client with support for the AWS SDK for Java 2.x! Check it out here:
11/17/23 Update: A new Database Encryption client was launched with support for the AWS SDK for Java 2.x, and it's also maintained by the AWS Crypto Tools team. For more info:
The text was updated successfully, but these errors were encountered: