Problem Description When attaching AWS S3 bucket as a backend for config service it attempts to initialize: AwsS3EnvironmentRepositoryFactory which is still using com.amazonaws.services.s3.AmazonS3ClientBuilder which is AWS SDKv1 where AWS recommend's to use new SDKv2 with software.amazon.awssdk.services.s3.S3ClientBuilder We are using some of SSM features and for that already imported SDKv2, but now we need to integrate two SDK's - v1 and v2 or rewrite everything SSM related to SDK1 - which sounds like an inappropriate decision.

Proposed Solution Spring Cloud Config should start using AWS SDKv2 when accessing AWS resources

Comment From: ryanjbaxter

Interested in contributing a PR?

Comment From: Bryksin

Would love to, but not now, I already have several projects in parallel, just no time for another, though I will consider

Comment From: eddumelendez

Hi @ryanjbaxter is it ok if we have 2 modules for aws, one for sdk v1 and other for sdk v2?

Comment From: ryanjbaxter

Well we currently don't have a separate module...I am fine with removing sdk v1 in the main branch all together

Comment From: Bryksin

I still remember about PR invitation 😃 Hope I will find time soon!

Comment From: hpoettker

Spring Vault has released 3.0.0-M1 and switched to v2. If I'm not mistaken, this precludes the possibility to stay (exclusively) on v1 in 4.x due to the dependency on Spring Vault. Switching completely seems the best option to me.