-
Notifications
You must be signed in to change notification settings - Fork 653
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
Missing docs on how to migrate from s3crypto #1636
Comments
Thanks for reaching out @junedev. The v2 SDK does not provide an comparable module to the v1 SDK's S3 encryption client provided by v1. How or when feature would be created to be compatible with the v2 SDK is still being evaluated by the SDK team. We can use this GitHub issue to track that feature. |
Hi, is there any update on this feature ? |
@jasdel Hi, is there any update on this feature ? |
@jasdel and v1 sdk dont support multipart upload with client-side encryption, is there any plan ? |
Thanks for reaching out @pinple. Crypto support for v2 SDK is a backlog item that is being investigated. I don't have any updates available to share at the moment for this. With regard to multipart upload, this is a pending backlog item for the SDK team to evaluate. |
Hey @jasdel, could you please let me know if there are any new developments or timelines for this issue? I would appreciate any information you can provide. Thank you for your time and assistance. |
There is no update to provide at the moment. This is still a backlog issue that we are actively looking into but no ETA at the moment. Stay tuned. |
AWS Crypto Tools recently released the 3.x encryption client: https://github.com/aws/amazon-s3-encryption-client-go, which is compatible with the v2 SDK. I've added a section on migrating in this devguide refresh: #2431. |
|
Describe the issue with documentation
We currently use the s3crypto package of the v1 Go SDK in our production system. We would like to migrate to the new V2 SDK, however the s3crypto package is not part of the new SDK anymore. The AWS encryption SDK does not exist for Go.
Currently the migration guide does not mention the removal of s3crypto at all although this clearly a breaking change.
It would be great to get some advice whether a replacement in Go will be provided at a later point in time and if not, what is the recommended course of action for customers that currently use s3crypto?
[Same question was asked here]
Suggestion
No response
AWS Go SDK version used
No response
The text was updated successfully, but these errors were encountered: