upgrade-aws-sdk-v2_skill

Overview

This skill helps migrate Java projects from AWS SDK v1 (com.amazonaws) to AWS SDK v2 (software.amazon.awssdk). It provides a practical migration strategy, quick commands to find and replace v1 usage, and recommended dependency changes to minimize code churn. Use it to remove deprecated v1 imports, resolve dependency conflicts, and adopt v2 features like async clients and HTTP/2.

How this skill works

The skill inspects source files and Gradle/Maven dependencies to locate com.amazonaws imports and transitive v1 artifacts. It recommends a priority-ordered migration strategy: prefer library updates, then BOM overrides, then dependency substitution, and finally direct code changes. It includes concrete Gradle snippets for dependency substitution and validation commands to confirm removal of v1 usage.

When to use it

• Project contains imports starting with com.amazonaws.*
• Dependabot or security scans flag AWS SDK v1 vulnerabilities
• You need v2-only features such as async clients or HTTP/2
• Upgrading libraries or platform BOMs to eliminate v1 transitive dependencies
• Deliverable requests explicitly require migrating to AWS SDK v2

Best practices

• Prefer upgrading dependent libraries to versions that already use SDK v2 before changing code.
• Check BOMs (Spring Boot, corporate BOMs) for v1 overrides and update BOM or use dependency management to force v2.
• Use dependency substitution at the build root to replace v1 artifacts with v2 equivalents when library updates are not available.
• Run grep and dependency tree checks early and after changes to validate no com.amazonaws imports remain.
• Update related plugins or connectors (example: aws-msk-iam-auth) to v2-compatible versions to avoid NoClassDefFoundError.

Example use cases

• A legacy service uses S3 and SQS via com.amazonaws; replace transitive v1 dependencies and migrate usage to software.amazon.awssdk clients.
• A monorepo where a Spring Boot BOM pulls in aws-java-sdk modules; override the BOM to point to v2 or update the BOM version.
• A security audit flags v1; use dependency substitution and quick validation commands to remediate and rebuild.
• Migrating Kafka MSK IAM authentication: update aws-msk-iam-auth to a v2-compatible release to prevent AWSCredentialsProvider errors.