Why do I receive errors when I run AWS CLI commands?

Resolution

• Verify that you have the latest version of the AWS CLI installed. The AWS CLI updates frequently. When you run an earlier CLI version, you can't access newer released features. For more information, see Confirm that you're running a recent version of the AWS CLI.
• Make sure that the AWS Identity and Access Management (IAM) role or IAM user has the correct permissions to run the relevant commands. For instructions on how to do this, see How can I decode an authorization failure message after receiving an "UnauthorizedOperation" error during an EC2 instance launch?
• Make sure that the time on your host machine is correct.
  For Linux, see Set the time for your Linux instance.
  For Windows, see Set the time for a Windows instance.
• Make sure that you're using the correct AWS Security Token Service (AWS STS) token format. For more information, see Why did I receive the IAM error "AWS was not able to validate the provided access credentials" in some AWS Regions?
• Make sure that you're using the correct credentials to make the API call. If there are multiple sets of credentials on the instance, then credential precedence might affect which credentials the instance uses to make the API call. To verify the set of credentials in use, run the aws sts get-caller-identity command. For more information, see Why is my Amazon EC2 instance using IAM user credentials instead of role credentials?
• If there are any errors, see Troubleshoot AWS CLI errors and Why can't I run AWS CLI commands on my EC2 instance?