public interface AWSSecurityTokenServiceAsync extends AWSSecurityTokenService
The AWS Security Token Service is a web service that enables you to request temporary, limited-privilege credentials for AWS Identity and Access Management (IAM) users or for users that you authenticate (federated users). This guide provides descriptions of the AWS Security Token Service API.
For more detailed information about using this service, go to Using Temporary Security Credentials .
For information about setting up signatures and authorization through the API, go to Signing AWS API Requests in the AWS General Reference . For general information about the Query API, go to Making Query Requests in Using IAM . For information about using security tokens with other AWS products, go to Using Temporary Security Credentials to Access AWS in Using Temporary Security Credentials .
If you're new to AWS and need additional technical information about a specific AWS product, you can find the product's technical documentation at http://aws.amazon.com/documentation/ .
We will refer to Amazon Identity and Access Management using the abbreviated form IAM. All copyrights and legal protections still apply.
| 修飾子とタイプ | メソッドと説明 |
|---|---|
java.util.concurrent.Future<AssumeRoleResult> |
assumeRoleAsync(AssumeRoleRequest assumeRoleRequest)
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) that you can
use to access AWS resources that you might not normally have access
to.
|
java.util.concurrent.Future<AssumeRoleResult> |
assumeRoleAsync(AssumeRoleRequest assumeRoleRequest,
AsyncHandler<AssumeRoleRequest,AssumeRoleResult> asyncHandler)
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) that you can
use to access AWS resources that you might not normally have access
to.
|
java.util.concurrent.Future<AssumeRoleWithWebIdentityResult> |
assumeRoleWithWebIdentityAsync(AssumeRoleWithWebIdentityRequest assumeRoleWithWebIdentityRequest)
Returns a set of temporary security credentials for users who have
been authenticated in a mobile or web application with a web identity
provider, such as Login with Amazon, Facebook, or Google.
|
java.util.concurrent.Future<AssumeRoleWithWebIdentityResult> |
assumeRoleWithWebIdentityAsync(AssumeRoleWithWebIdentityRequest assumeRoleWithWebIdentityRequest,
AsyncHandler<AssumeRoleWithWebIdentityRequest,AssumeRoleWithWebIdentityResult> asyncHandler)
Returns a set of temporary security credentials for users who have
been authenticated in a mobile or web application with a web identity
provider, such as Login with Amazon, Facebook, or Google.
|
java.util.concurrent.Future<DecodeAuthorizationMessageResult> |
decodeAuthorizationMessageAsync(DecodeAuthorizationMessageRequest decodeAuthorizationMessageRequest)
Decodes additional information about the authorization status of a
request from an encoded message returned in response to an AWS
request.
|
java.util.concurrent.Future<DecodeAuthorizationMessageResult> |
decodeAuthorizationMessageAsync(DecodeAuthorizationMessageRequest decodeAuthorizationMessageRequest,
AsyncHandler<DecodeAuthorizationMessageRequest,DecodeAuthorizationMessageResult> asyncHandler)
Decodes additional information about the authorization status of a
request from an encoded message returned in response to an AWS
request.
|
java.util.concurrent.Future<GetFederationTokenResult> |
getFederationTokenAsync(GetFederationTokenRequest getFederationTokenRequest)
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) for a
federated user.
|
java.util.concurrent.Future<GetFederationTokenResult> |
getFederationTokenAsync(GetFederationTokenRequest getFederationTokenRequest,
AsyncHandler<GetFederationTokenRequest,GetFederationTokenResult> asyncHandler)
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) for a
federated user.
|
java.util.concurrent.Future<GetSessionTokenResult> |
getSessionTokenAsync(GetSessionTokenRequest getSessionTokenRequest)
Returns a set of temporary credentials for an AWS account or IAM
user.
|
java.util.concurrent.Future<GetSessionTokenResult> |
getSessionTokenAsync(GetSessionTokenRequest getSessionTokenRequest,
AsyncHandler<GetSessionTokenRequest,GetSessionTokenResult> asyncHandler)
Returns a set of temporary credentials for an AWS account or IAM
user.
|
assumeRole, assumeRoleWithWebIdentity, decodeAuthorizationMessage, getCachedResponseMetadata, getFederationToken, getSessionToken, getSessionToken, setEndpoint, setRegion, shutdownjava.util.concurrent.Future<GetSessionTokenResult> getSessionTokenAsync(GetSessionTokenRequest getSessionTokenRequest) throws AmazonServiceException, AmazonClientException
Returns a set of temporary credentials for an AWS account or IAM
user. The credentials consist of an access key ID, a secret access
key, and a security token. Typically, you use
GetSessionToken if you want use MFA to protect
programmatic calls to specific AWS APIs like Amazon EC2
StopInstances . MFA-enabled IAM users would need to call
GetSessionToken and submit an MFA code that is associated
with their MFA device. Using the temporary security credentials that
are returned from the call, IAM users can then make programmatic calls
to APIs that require MFA authentication.
The GetSessionToken action must be called by using the
long-term AWS security credentials of the AWS account or an IAM user.
Credentials that are created by IAM users are valid for the duration
that you specify, between 900 seconds (15 minutes) and 129600 seconds
(36 hours); credentials that are created by using account credentials
have a maximum duration of 3600 seconds (1 hour).
The permissions that are granted to the federated user are the
intersection of the policy that is passed with the
GetSessionToken request and policies that are associated
with of the entity making the GetSessionToken call.
For more information about using GetSessionToken to
create temporary credentials, go to
Creating Temporary Credentials to Enable Access for IAM Users in
Using IAM .
getSessionTokenRequest - Container for the necessary parameters
to execute the GetSessionToken operation on AWSSecurityTokenService.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<GetSessionTokenResult> getSessionTokenAsync(GetSessionTokenRequest getSessionTokenRequest, AsyncHandler<GetSessionTokenRequest,GetSessionTokenResult> asyncHandler) throws AmazonServiceException, AmazonClientException
Returns a set of temporary credentials for an AWS account or IAM
user. The credentials consist of an access key ID, a secret access
key, and a security token. Typically, you use
GetSessionToken if you want use MFA to protect
programmatic calls to specific AWS APIs like Amazon EC2
StopInstances . MFA-enabled IAM users would need to call
GetSessionToken and submit an MFA code that is associated
with their MFA device. Using the temporary security credentials that
are returned from the call, IAM users can then make programmatic calls
to APIs that require MFA authentication.
The GetSessionToken action must be called by using the
long-term AWS security credentials of the AWS account or an IAM user.
Credentials that are created by IAM users are valid for the duration
that you specify, between 900 seconds (15 minutes) and 129600 seconds
(36 hours); credentials that are created by using account credentials
have a maximum duration of 3600 seconds (1 hour).
The permissions that are granted to the federated user are the
intersection of the policy that is passed with the
GetSessionToken request and policies that are associated
with of the entity making the GetSessionToken call.
For more information about using GetSessionToken to
create temporary credentials, go to
Creating Temporary Credentials to Enable Access for IAM Users in
Using IAM .
getSessionTokenRequest - Container for the necessary parameters
to execute the GetSessionToken operation on AWSSecurityTokenService.asyncHandler - Asynchronous callback handler for events in the
life-cycle of the request. Users could provide the implementation of
the four callback methods in this interface to process the operation
result or handle the exception.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<DecodeAuthorizationMessageResult> decodeAuthorizationMessageAsync(DecodeAuthorizationMessageRequest decodeAuthorizationMessageRequest) throws AmazonServiceException, AmazonClientException
Decodes additional information about the authorization status of a request from an encoded message returned in response to an AWS request.
For example, if a user is not authorized to perform an action that he
or she has requested, the request returns a
Client.UnauthorizedOperation response (an HTTP 403
response). Some AWS actions additionally return an encoded message
that can provide details about this authorization failure.
NOTE: Only certain AWS actions return an encoded authorization message. The documentation for an individual action indicates whether that action returns an encoded message in addition to returning an HTTP code.
The message is encoded because the details of the authorization status
can constitute privileged information that the user who requested the
action should not see. To decode an authorization status message, a
user must be granted permissions via an IAM policy to request the
DecodeAuthorizationMessage (
sts:DecodeAuthorizationMessage )
action.
The decoded message includes the following type of information:
decodeAuthorizationMessageRequest - Container for the necessary
parameters to execute the DecodeAuthorizationMessage operation on
AWSSecurityTokenService.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<DecodeAuthorizationMessageResult> decodeAuthorizationMessageAsync(DecodeAuthorizationMessageRequest decodeAuthorizationMessageRequest, AsyncHandler<DecodeAuthorizationMessageRequest,DecodeAuthorizationMessageResult> asyncHandler) throws AmazonServiceException, AmazonClientException
Decodes additional information about the authorization status of a request from an encoded message returned in response to an AWS request.
For example, if a user is not authorized to perform an action that he
or she has requested, the request returns a
Client.UnauthorizedOperation response (an HTTP 403
response). Some AWS actions additionally return an encoded message
that can provide details about this authorization failure.
NOTE: Only certain AWS actions return an encoded authorization message. The documentation for an individual action indicates whether that action returns an encoded message in addition to returning an HTTP code.
The message is encoded because the details of the authorization status
can constitute privileged information that the user who requested the
action should not see. To decode an authorization status message, a
user must be granted permissions via an IAM policy to request the
DecodeAuthorizationMessage (
sts:DecodeAuthorizationMessage )
action.
The decoded message includes the following type of information:
decodeAuthorizationMessageRequest - Container for the necessary
parameters to execute the DecodeAuthorizationMessage operation on
AWSSecurityTokenService.asyncHandler - Asynchronous callback handler for events in the
life-cycle of the request. Users could provide the implementation of
the four callback methods in this interface to process the operation
result or handle the exception.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<AssumeRoleWithWebIdentityResult> assumeRoleWithWebIdentityAsync(AssumeRoleWithWebIdentityRequest assumeRoleWithWebIdentityRequest) throws AmazonServiceException, AmazonClientException
Returns a set of temporary security credentials for users who have
been authenticated in a mobile or web application with a web identity
provider, such as Login with Amazon, Facebook, or Google.
AssumeRoleWithWebIdentity is an API call that does not
require the use of AWS security credentials. Therefore, you can
distribute an application (for example, on mobile devices) that
requests temporary security credentials without including long-term
AWS credentials in the application or by deploying server-based proxy
services that use long-term AWS credentials. For more information, see
Creating a Mobile Application with Third-Party Sign-In in AWS
Security Token Service .
The temporary security credentials consist of an access key ID, a
secret access key, and a security token. Applications can use these
temporary security credentials to sign calls to AWS service APIs. The
credentials are valid for the duration that you specified when calling
AssumeRoleWithWebIdentity , which can be from 900 seconds
(15 minutes) to 3600 seconds (1 hour). By default, the temporary
security credentials are valid for 1 hour.
The temporary security credentials that are returned from the
AssumeRoleWithWebIdentity response have the permissions
that are associated with the access policy of the role being assumed.
You can further restrict the permissions of the temporary security
credentials by passing a policy in the request. The resulting
permissions are an intersection of the role's access policy and the
policy that you passed. These policies and any applicable
resource-based policies are evaluated when calls to AWS service APIs
are made using the temporary security credentials.
Before your application can call
AssumeRoleWithWebIdentity , you must have an identity
token from a supported identity provider and create a role that the
application can assume. The role that your application assumes must
trust the identity provider that is associated with the identity
token. In other words, the identity provider must be specified in the
role's trust policy. For more information, see
Creating Temporary Security Credentials for Mobile Apps Using
Third-Party Identity Providers .
assumeRoleWithWebIdentityRequest - Container for the necessary
parameters to execute the AssumeRoleWithWebIdentity operation on
AWSSecurityTokenService.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<AssumeRoleWithWebIdentityResult> assumeRoleWithWebIdentityAsync(AssumeRoleWithWebIdentityRequest assumeRoleWithWebIdentityRequest, AsyncHandler<AssumeRoleWithWebIdentityRequest,AssumeRoleWithWebIdentityResult> asyncHandler) throws AmazonServiceException, AmazonClientException
Returns a set of temporary security credentials for users who have
been authenticated in a mobile or web application with a web identity
provider, such as Login with Amazon, Facebook, or Google.
AssumeRoleWithWebIdentity is an API call that does not
require the use of AWS security credentials. Therefore, you can
distribute an application (for example, on mobile devices) that
requests temporary security credentials without including long-term
AWS credentials in the application or by deploying server-based proxy
services that use long-term AWS credentials. For more information, see
Creating a Mobile Application with Third-Party Sign-In in AWS
Security Token Service .
The temporary security credentials consist of an access key ID, a
secret access key, and a security token. Applications can use these
temporary security credentials to sign calls to AWS service APIs. The
credentials are valid for the duration that you specified when calling
AssumeRoleWithWebIdentity , which can be from 900 seconds
(15 minutes) to 3600 seconds (1 hour). By default, the temporary
security credentials are valid for 1 hour.
The temporary security credentials that are returned from the
AssumeRoleWithWebIdentity response have the permissions
that are associated with the access policy of the role being assumed.
You can further restrict the permissions of the temporary security
credentials by passing a policy in the request. The resulting
permissions are an intersection of the role's access policy and the
policy that you passed. These policies and any applicable
resource-based policies are evaluated when calls to AWS service APIs
are made using the temporary security credentials.
Before your application can call
AssumeRoleWithWebIdentity , you must have an identity
token from a supported identity provider and create a role that the
application can assume. The role that your application assumes must
trust the identity provider that is associated with the identity
token. In other words, the identity provider must be specified in the
role's trust policy. For more information, see
Creating Temporary Security Credentials for Mobile Apps Using
Third-Party Identity Providers .
assumeRoleWithWebIdentityRequest - Container for the necessary
parameters to execute the AssumeRoleWithWebIdentity operation on
AWSSecurityTokenService.asyncHandler - Asynchronous callback handler for events in the
life-cycle of the request. Users could provide the implementation of
the four callback methods in this interface to process the operation
result or handle the exception.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<GetFederationTokenResult> getFederationTokenAsync(GetFederationTokenRequest getFederationTokenRequest) throws AmazonServiceException, AmazonClientException
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) for a
federated user. A typical use is in a proxy application that is
getting temporary security credentials on behalf of distributed
applications inside a corporate network. Because you must call the
GetFederationToken action using the long-term security
credentials of an IAM user, this call is appropriate in contexts where
those credentials can be safely stored, usually in a server-based
application.
Note: Do not use this call in mobile applications or
client-based web applications that directly get temporary security
credentials. For those types of applications, use
AssumeRoleWithWebIdentity .
The GetFederationToken action must be called by using
the long-term AWS security credentials of the AWS account or an IAM
user. Credentials that are created by IAM users are valid for the
specified duration, between 900 seconds (15 minutes) and 129600
seconds (36 hours); credentials that are created by using account
credentials have a maximum duration of 3600 seconds (1 hour).
The permissions that are granted to the federated user are the
intersection of the policy that is passed with the
GetFederationToken request and policies that are
associated with of the entity making the
GetFederationToken call.
For more information about how permissions work, see
Controlling Permissions in Temporary Credentials in Using
Temporary Security Credentials . For information about using
GetFederationToken to create temporary security
credentials, see
Creating Temporary Credentials to Enable Access for Federated Users
in Using Temporary Security Credentials .
getFederationTokenRequest - Container for the necessary
parameters to execute the GetFederationToken operation on
AWSSecurityTokenService.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<GetFederationTokenResult> getFederationTokenAsync(GetFederationTokenRequest getFederationTokenRequest, AsyncHandler<GetFederationTokenRequest,GetFederationTokenResult> asyncHandler) throws AmazonServiceException, AmazonClientException
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) for a
federated user. A typical use is in a proxy application that is
getting temporary security credentials on behalf of distributed
applications inside a corporate network. Because you must call the
GetFederationToken action using the long-term security
credentials of an IAM user, this call is appropriate in contexts where
those credentials can be safely stored, usually in a server-based
application.
Note: Do not use this call in mobile applications or
client-based web applications that directly get temporary security
credentials. For those types of applications, use
AssumeRoleWithWebIdentity .
The GetFederationToken action must be called by using
the long-term AWS security credentials of the AWS account or an IAM
user. Credentials that are created by IAM users are valid for the
specified duration, between 900 seconds (15 minutes) and 129600
seconds (36 hours); credentials that are created by using account
credentials have a maximum duration of 3600 seconds (1 hour).
The permissions that are granted to the federated user are the
intersection of the policy that is passed with the
GetFederationToken request and policies that are
associated with of the entity making the
GetFederationToken call.
For more information about how permissions work, see
Controlling Permissions in Temporary Credentials in Using
Temporary Security Credentials . For information about using
GetFederationToken to create temporary security
credentials, see
Creating Temporary Credentials to Enable Access for Federated Users
in Using Temporary Security Credentials .
getFederationTokenRequest - Container for the necessary
parameters to execute the GetFederationToken operation on
AWSSecurityTokenService.asyncHandler - Asynchronous callback handler for events in the
life-cycle of the request. Users could provide the implementation of
the four callback methods in this interface to process the operation
result or handle the exception.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<AssumeRoleResult> assumeRoleAsync(AssumeRoleRequest assumeRoleRequest) throws AmazonServiceException, AmazonClientException
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) that you can
use to access AWS resources that you might not normally have access
to. Typically, you use AssumeRole for cross-account
access or federation.
For cross-account access, imagine that you own multiple accounts and need to access resources in each account. You could create long-term credentials in each account to access those resources. However, managing all those credentials and remembering which one can access which account can be time consuming. Instead, you can create one set of long-term credentials in one account and then use temporary security credentials to access all the other accounts by assuming roles in those accounts. For more information about roles, see Roles in Using IAM .
For federation, you can, for example, grant single sign-on access to
the AWS Management Console. If you already have an identity and
authentication system in your corporate network, you don't have to
recreate user identities in AWS in order to grant those user
identities access to AWS. Instead, after a user has been
authenticated, you call AssumeRole (and specify the role
with the appropriate permissions) to get temporary security
credentials for that user. With those temporary security credentials,
you construct a sign-in URL that users can use to access the console.
For more information, see
Scenarios for Granting Temporary Access in AWS Security Token
Service .
The temporary security credentials are valid for the duration that
you specified when calling AssumeRole , which can be from
900 seconds (15 minutes) to 3600 seconds (1 hour). The default is 1
hour.
The temporary security credentials that are returned from the
AssumeRoleWithWebIdentity response have the permissions
that are associated with the access policy of the role being assumed
and any policies that are associated with the AWS resource being
accessed. You can further restrict the permissions of the temporary
security credentials by passing a policy in the request. The resulting
permissions are an intersection of the role's access policy and the
policy that you passed. These policies and any applicable
resource-based policies are evaluated when calls to AWS service APIs
are made using the temporary security credentials.
To assume a role, your AWS account must be trusted by the role. The
trust relationship is defined in the role's trust policy when the IAM
role is created. You must also have a policy that allows you to call
sts:AssumeRole .
Important: You cannot call Assumerole by using
AWS account credentials; access will be denied. You must use IAM user
credentials or temporary security credentials to call
AssumeRole .
assumeRoleRequest - Container for the necessary parameters to
execute the AssumeRole operation on AWSSecurityTokenService.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.java.util.concurrent.Future<AssumeRoleResult> assumeRoleAsync(AssumeRoleRequest assumeRoleRequest, AsyncHandler<AssumeRoleRequest,AssumeRoleResult> asyncHandler) throws AmazonServiceException, AmazonClientException
Returns a set of temporary security credentials (consisting of an
access key ID, a secret access key, and a security token) that you can
use to access AWS resources that you might not normally have access
to. Typically, you use AssumeRole for cross-account
access or federation.
For cross-account access, imagine that you own multiple accounts and need to access resources in each account. You could create long-term credentials in each account to access those resources. However, managing all those credentials and remembering which one can access which account can be time consuming. Instead, you can create one set of long-term credentials in one account and then use temporary security credentials to access all the other accounts by assuming roles in those accounts. For more information about roles, see Roles in Using IAM .
For federation, you can, for example, grant single sign-on access to
the AWS Management Console. If you already have an identity and
authentication system in your corporate network, you don't have to
recreate user identities in AWS in order to grant those user
identities access to AWS. Instead, after a user has been
authenticated, you call AssumeRole (and specify the role
with the appropriate permissions) to get temporary security
credentials for that user. With those temporary security credentials,
you construct a sign-in URL that users can use to access the console.
For more information, see
Scenarios for Granting Temporary Access in AWS Security Token
Service .
The temporary security credentials are valid for the duration that
you specified when calling AssumeRole , which can be from
900 seconds (15 minutes) to 3600 seconds (1 hour). The default is 1
hour.
The temporary security credentials that are returned from the
AssumeRoleWithWebIdentity response have the permissions
that are associated with the access policy of the role being assumed
and any policies that are associated with the AWS resource being
accessed. You can further restrict the permissions of the temporary
security credentials by passing a policy in the request. The resulting
permissions are an intersection of the role's access policy and the
policy that you passed. These policies and any applicable
resource-based policies are evaluated when calls to AWS service APIs
are made using the temporary security credentials.
To assume a role, your AWS account must be trusted by the role. The
trust relationship is defined in the role's trust policy when the IAM
role is created. You must also have a policy that allows you to call
sts:AssumeRole .
Important: You cannot call Assumerole by using
AWS account credentials; access will be denied. You must use IAM user
credentials or temporary security credentials to call
AssumeRole .
assumeRoleRequest - Container for the necessary parameters to
execute the AssumeRole operation on AWSSecurityTokenService.asyncHandler - Asynchronous callback handler for events in the
life-cycle of the request. Users could provide the implementation of
the four callback methods in this interface to process the operation
result or handle the exception.AmazonClientException - If any internal errors are encountered inside the client while
attempting to make the request or handle the response. For example
if a network connection is not available.AmazonServiceException - If an error response is returned by AWSSecurityTokenService indicating
either a problem with the data in the request, or a server side issue.