[Question] Migrating from 2 to 3

[pedrofurlanetto90]

Problem:

Hello team

I'm migrating from SDK V2 to V3 and currently, I'm using encrypt and decryptData methods with a CachingCryptoMaterialsManager. These methods are deprecated in V3, my questions are:

1. What cache mechanism should I use to keep the same behavior? Is it AwsKmsHierarchicalKeyring? I didn't find a documentation for this
2. How can I migrate without breaking the compatibility? When I promote the changes to production I must be able to continue decrypting old items in the queue for a while. There is no guide to migrate to V3 like other AWS SDKs have to help with this task

Thanks.

[lucasmcdonald3]

Hi @pedrofurlanetto90 --

There is currently no equivalent cache mechanism that can be used with components from the MPL. Any applications that have already integrated with the now-deprecated CachingCryptoMaterialsManager are blocked from adopting MPL components until we (AWS Crypto Tools) release the caching CMM in the AWS Cryptographic Material Providers Library (MPL).

[pedrofurlanetto90]

Hi @lucasmcdonald3, thanks for the answer. Do you have an ETA for that? According to https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/, AWS SDK V1 will reach end-of-support on December 31, 2025. We are working to remove AWS SDK V1 from our code, and it requires migration to AWS Encryptyon SDK V3