Migrating AWS S3 SDK to v2 #1402
Description
As reported at #1168 (review), our optional dependency AWS S3 client SDK must be migraded to its v2 by the end of 2025.
Both groupId and artifactId are different:
- <groupId>com.amazonaws</groupId>
- <artifactId>aws-java-sdk-s3</artifactId>
+ <groupId>software.amazon.awssdk</groupId>
+ <artifactId>s3</artifactId>Here is a version range example:
- <aws.s3.version>[1.12.62,1.13.0)</aws.s3.version>
+ <aws.s3.version>[2.29.24,3)</aws.s3.version>V2 is fully source-code incompatible, so this work requires rewriting the modules relying on the AWS SDK plus testing the behavior is still the same. It seems there is no need to migrate "aws-lambda-java-core" to something new this time.
See also:
- https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/migration.html
- https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/migration-service-changes.html
- https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/migration-client-credentials.html
- https://docs.aws.amazon.com/lambda/latest/dg/lambda-java.html
We may want to try the migration tool if it works well for us:
Category (place an x in each of the [ ])
- bolt (Bolt for Java)
- bolt-{sub modules} (Bolt for Java - optional modules)
- slack-api-client (Slack API Clients)
- slack-api-model (Slack API Data Models)
- slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
- slack-app-backend (The primitive layer of Bolt for Java)
Requirements
Please make sure if this topic is specific to this SDK. For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. 🙇
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.