Skip navigation links

AWS SDK for Java 1.x API Reference - 1.12.731

We announced the upcoming end-of-support for AWS SDK for Java (v1). We recommend that you migrate to AWS SDK for Java v2. For dates, additional details, and information on how to migrate, please refer to the linked announcement.

Package com.amazonaws.auth.profile

AWS configuration profiles allow you to share multiple sets of AWS security credentials between different tools such as the AWS SDK for Java and the AWS CLI.

See: Description

Package com.amazonaws.auth.profile Description

AWS configuration profiles allow you to share multiple sets of AWS security credentials between different tools such as the AWS SDK for Java and the AWS CLI.

In addition to the required default profile, you can specify as many additional named profiles as you need:

 [default]
 aws_access_key_id=AKIAXXXXXXXXXX
 aws_secret_access_key=abc01234567890

 [profile test]
 aws_access_key_id=AKIAZZZZZZZZZZ
 aws_secret_access_key=xyz01234567890
 

Role assumption is also supported for cross account access. The source profile credentials are used to assume the given role when the

test
profile is used. One requirement to use assume role profiles is that the STS SDK module be on the class path.
 [default]
 aws_access_key_id=AKIAXXXXXXXXXX
 aws_secret_access_key=abc01234567890

 [profile test]
 role_arn=arn:aws:iam::123456789012:role/role-name
 source_profile=default
 # Optionally, provide a session name
 # role_session_name=mysession
 # Optionally, provide an external id
 # external_id=abc01234567890
 

You can use ProfileCredentialsProvider to access your AWS configuration profiles and supply your credentials to code using the AWS SDK for Java.

The same profiles are used by the AWS CLI.

For more information on setting up AWS configuration profiles, see: http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html

Skip navigation links