Java applications using the AWS SDK for Java running on an Amazon Elastic Compute Cloud (Amazon EC2) instance might experience an exception similar to the following:

com.amazonaws.AmazonServiceException: The security token included in the request is expired (Service: AmazonSQS; Status Code: 403; Error Code: ExpiredToken; Request ID: 12a345b6-78cd-901e-fg23-45hi67890jkl)

All application API requests to Amazon Web Services (AWS) must be cryptographically signed using credentials issued by AWS.

If your application uses temporary credentials when creating an AWS client (such as an AmazonSQS client), the credentials expire at the time interval specified during their creation. You must make sure that the credentials are refreshed before they expire.

Another reason for expiration is using the incorrect time. A consistent and accurate time reference is crucial for many server tasks and processes. If your instance's date and time aren't set correctly, the AWS credentials might be rejected.

If your application is running on an Amazon EC2 instance, we recommend using an AWS Identity and Access Management (IAM) role assigned to the instance. Using an IAM role allows the use of a default service constructor. The default constructor client searches for credentials by using the default credentials provider chain, in the following order:

  1. In system environment variables: AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
  2. In the Java system properties: aws.accessKeyId and aws.secretKey.
  3. In the default credentials file (the location of this file varies by platform).
  4. In the instance profile credentials contained in the instance metadata associated with the IAM role for the EC2 instance. Instance profile credentials are added to the default credentials provider chain when you attach an instance profile to your instance. For more information, see Using an IAM Role to Grant Permissions to Applications Running on Amazon EC2 Instances.

If instance profile credentials are available, the default client constructor creates an instance of the AWS SDK InstanceProfileCredentialsProvider class. This class is used to sign API requests with AWS credentials using temporary security credentials from Amazon EC2 instance metadata.

Important: If your application uses the AWS SDK ProfileCredentialsProvider class to provide temporary AWS credentials, you are responsible for checking for and refreshing credentials before they expire. Not checking or refreshing your credentials can increase the likelihood of application failures caused by ExpiredToken errors.

Use Amazon Time Sync Service or NTP sources

To make sure that your Linux instance has a consistent and accurate time reference, configure the Amazon Time Sync Service, or another Network Time Protocol (NTP) source on your Amazon EC2 instance. For more information, see Setting the Time for Your Linux Instance, or Setting the Time for a Windows Instance.

Use custom temporary AWS credentials

Refresh temporary credentials five minutes before their expiration.

Use an IAM role assigned to an instance

Attach an instance profile to your instance. For more information, see Using an IAM Role to Grant Permissions to Applications Running on Amazon EC2 Instances. Verify in your code as well as on the instance that no other credentials are specified. The instance profile credentials are the last place the default credential provider chain searches for credentials. If you have credentials located anywhere earlier in the search chain it will prevent the IAM from being used. For more information, see Working with AWS Credentials.

To see the AWS credentials for an IAM role that's attached to an instance, run the following commands from a Linux shell or from Windows PowerShell (v3.0 or later). Be sure to replace examplerole with the name of your IAM role.

For Linux, use the curl command to see AWS credentials:

$ curl http://169.254.169.254/latest/meta-data/iam/security-credentials/examplerole

This command returns output similar to the following:

{

     "Code" : "Success",

     "LastUpdated" : "2016-04-26T16:39:16Z",

     "Type" : "AWS-HMAC",

     "AccessKeyId" : "AKIAIOSFODNN7EXAMPLE",

     "SecretAccessKey" : "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY",

     "Token" : "token",

     "Expiration" : "2016-04-27T22:39:16Z"

}

For Windows, use the Invoke-RestMethod command to see AWS credentials:

PS C:\> Invoke-RestMethod http://169.254.169.254/latest/meta-data/iam/security-credentials/examplerole

This command returns output similar to the following:

Code            : Success

LastUpdated     : 2016-07-18T18:09:47Z

Type            : AWS-HMAC

AccessKeyId     : AKIAIOSFODNN7EXAMPLE

SecretAccessKey : wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

Token           : token

Expiration      : 2016-04-27T22:39:16Z

Use these commands to check the latest temporary credentials for the instance. These credentials are automatically rotated or refreshed approximately five minutes before the expiration of the assigned temporary credentials.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-07-19

Updated: 2018-11-06