Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon SAM CLI troubleshooting

This section provides details on how to troubleshoot error messages when using, installing, and managing the Amazon Serverless Application Model Command Line Interface (Amazon SAM CLI).

Troubleshooting

For troubleshooting guidance related to Amazon SAM CLI, see Troubleshooting installation errors.

Error messages

Curl error: "curl: (6) Could not resolve: ..."

When trying to invoke the API Gateway endpoint, you see the following error:

curl: (6) Could not resolve: endpointdomain (Domain name not found)

This means that you've attempted to send a request to a domain that's not valid. This can happen if your serverless application failed to deploy successfully, or if you have a typo in your curl command. Verify that the application deployed successfully by using the Amazon CloudFormation console or the Amazon CLI, and verify that your curl command is correct.

Error: Can’t find exact resource information with given stack name

When running the sam remote invoke command on an application that contains a single Lambda function resource, you see the following error:

Error: Can't find exact resource information with given <stack-name>. Please provide full resource ARN or --stack-name to resolve the ambiguity.

Error: Can’t find resource information from stack name

When running the sam remote invoke command and passing a Lambda function ARN as an argument, you see the following error:

Error: Can't find resource information from stack name (<stack-name>) and resource id (<function-id>)

Error: Failed to create managed resources: Unable to locate credentials

When running the sam deploy command, you see the following error:

Error: Failed to create managed resources: Unable to locate credentials

This means that you have not set up Amazon credentials to enable the Amazon SAM CLI to make Amazon service calls. To fix this, you must set up Amazon credentials. For more information, see Setting up Amazon credentials.

Error: FileNotFoundError in Windows

When running commands in Amazon SAM CLI on Windows, you may see the following error:

Error: FileNotFoundError

Possible cause: The Amazon SAM CLI might interact with filepaths that exceed the Windows max path limitation.

Solution: To resolve this issue, the new long paths behavior must enabled. To do this, see Enable Long Paths in Windows 10, Version 1607, and Later in the Microsoft Windows App Development Documentation.

Error: pip's dependency resolver ...

Example error text:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. 
aws-sam-cli 1.58.0 requires aws-sam-translator==1.51.0, but you have aws-sam-translator 1.58.0 which is incompatible. 
aws-sam-cli 1.58.0 requires typing-extensions==3.10.0.0, but you have typing-extensions 4.4.0 which is incompatible.

Error: No such command ‘remote’

When running the sam remote invoke command, you see the following error:

$ sam remote invoke ...
2023-06-20 08:15:07 Command remote not available
Usage: sam [OPTIONS] COMMAND [ARGS]...
Try 'sam -h' for help.

Error: No such command 'remote'.

Error: Running Amazon SAM projects locally requires Docker. Have you got it installed?

When running the sam local start-api command, you see the following error:

Error: Running Amazon SAM projects locally requires Docker. Have you got it installed?

This means that you do not have Docker properly installed. Docker is required to test your application locally. To fix this, follow the instructions for installing Docker for your development host. For more information, see Installing Docker.

Error: Security Constraints Not Satisfied

When running sam deploy --guided, you're prompted with the question Function may not have authorization defined, Is this okay? [y/N]. If you respond to this prompt with N (the default response), you see the following error:

Error: Security Constraints Not Satisfied

The prompt is informing you that the application you're about to deploy might have a publicly accessible Amazon API Gateway API configured without authorization. By responding N to this prompt, you're saying that this is not OK.

To fix this, you have the following options:

message: Missing Authentication Token

When trying to invoke the API Gateway endpoint, you see the following error:

{"message":"Missing Authentication Token"}

This means that you've attempted to send a request to the correct domain, but the URI isn't recognizable. To fix this, verify the full URL, and update the curl command with the correct URL.

Warning messages

Warning: ... Amazon will no longer maintain the Homebrew installer for Amazon SAM ...

When installing the Amazon SAM CLI using Homebrew, you see the following warning message:

Warning: ... Amazon will no longer maintain the Homebrew installer for Amazon SAM (aws/tap/aws-sam-cli). 
				For AWS supported installations, use the first party installers ...