Why can't I run AWS CLI commands on my EC2 instance?

3 minute read

Why am I receiving errors while trying to run AWS Command Line Interface (AWS CLI) commands on my Amazon Elastic Compute Cloud (Amazon EC2) instance?

Short description

When running AWS CLI commands on your instance, you might see one of the following error messages:

  • "Unable to locate credentials. You can configure credentials by running 'aws configure'"
  • "An error occurred (UnauthorizedOperation) when calling the DescribeInstances operation: You are not authorized to perform this operation"
  • "An error occurred (AuthFailure) when calling the DescribeInstances operation: AWS was not able to validate the provided access credentials"
  • "An error occurred (ExpiredToken) when calling the GetCallerIdentity operation: The security token included in the request is expired"

The operation listed in the error varies depending on the operation that you called when the error occurred. In the preceding examples, the errors occurred when calling the DescribeInstances and GetCallerIdentity operations.

Note: For communication issues between the AWS CLI and one of the AWS service endpoints, confirm that the DNS resolution and any VPC endpoints work correctly. For more information, see the following:


Verify that you're running the most recent AWS CLI version

If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

Unable to locate credentials

Verify that the AWS CLI is installed and configured correctly.

When using AWS Identity and Access Management (IAM) instance profiles, make sure that the IAM role association has completed.

An error occurred (UnauthorizedOperation) and (AuthFailure)

An error occurred (ExpiredToken)

Temporary credentials expire at the time interval specified during creation. If the credentials for your IAM role are expired, then obtain a new STS token by assuming a new IAM role.

Related information

How can I troubleshoot issues with an IAM policy?

AWS OFFICIALUpdated 2 years ago
No comments