The AWS SDK for Java 2.0 is a rewrite of 1.0 with some great new features. As with version 1.0, it enables you to easily work with Amazon Web Services but also includes features like non-blocking IO and pluggable HTTP implementation to further customize your applications. You can get started in minutes using Maven or any build system that supports MavenCentral as an artifact source.
- SDK Homepage
- 1.11 to 2.0 Changelog
- Best Practices
- Sample Code
- API Docs
- Developer Guide (source)
- Maven Archetypes
- Issues
- SDK Blog
- Giving Feedback
Before you begin, you need an AWS account. Please see the Sign Up for AWS section of the developer guide for information about how to create an AWS account and retrieve your AWS credentials.
To run the SDK you will need Java 1.8+. For more information about the requirements and optimum settings for the SDK, please see the Installing a Java Development Environment section of the developer guide.
The recommended way to use the AWS SDK for Java in your project is to consume it from Maven Central.
To automatically manage module versions (currently all modules have the same version, but this may not always be the case) we recommend you use the Bill of Materials import as follows:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>bom</artifactId>
<version>2.17.266</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
Then individual models may omit the version
from their dependency statement:
<dependencies>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>ec2</artifactId>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>s3</artifactId>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>dynamodb</artifactId>
</dependency>
</dependencies>
Alternatively you can add dependencies for the specific services you use only:
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>ec2</artifactId>
<version>2.17.266</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>s3</artifactId>
<version>2.17.266</version>
</dependency>
You can import the whole SDK into your project (includes ALL services). Please note that it is recommended to only import the modules you need.
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>aws-sdk-java</artifactId>
<version>2.17.266</version>
</dependency>
See the Set up the AWS SDK for Java section of the developer guide for more usage information.
-
Provides a way to plug in your own HTTP implementation.
-
Provides first class support for non-blocking IO in Async clients.
Once you check out the code from GitHub, you can build it using the following commands.
Linux:
./mvnw clean install
# Skip tests, checkstyles, findbugs, etc for quick build
./mvnw clean install -P quick
# Build a specific service module
./mvnw clean install -pl :s3 -P quick --am
Windows:
./mvnw.cmd clean install
You can find sample code for v2 in the following places:
- aws-doc-sdk-examples repo.
- Integration tests in this repo. They are located in the
it
directory under each service module, eg: s3-integration-tests
For information about maintenance and support for SDK major versions and their underlying dependencies, see the following in the AWS SDKs and Tools Reference Guide:
We maintain full support on Long-Term Support(LTS) releases: Java 8, Java 11, and Java 17.
We need your help in making this SDK great. Please participate in the community and contribute to this effort by submitting issues, participating in discussion forums and submitting pull requests through the following channels:
- Submit issues - this is the preferred channel to interact with our team
- Articulate your feature request or upvote existing ones on our Issues page
- Send feedback directly to the team at aws-java-sdk-v2-feedback@amazon.com
- Come join the AWS Java community chat on Gitter
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!