How can I troubleshoot the "Runtime.InvalidEntrypoint" error for my Lambda function that's from a Docker image?

2 分的閱讀內容

I received a "Runtime.InvalidEntrypoint" error when trying to create an AWS Lambda function from a Docker image.

Resolution

When the entry in the Lambda function configuration is incorrect, you receive the "Runtime.InvalidEntrypoint". To resolve this issue, check the following configuration settings for your Lambda function.

Verify that the ENTRYPOINT and CMD to your container image include the absolute path as the location and doesn't contain a symlink as the ENTRYPOINT. For more information, see Container: Error occurs on runtime InvalidEntrypoint.
Make sure that the ENTRYPOINT is correct in the Lambda function's configuration. Also, the ENTRYPOINT must match the command in the container's Dockerfile that's used for the runtime.
Verify that the container image is pushed to the correct Amazon Elastic Container Registry (Amazon ECR).
Make sure that the Docker image's architecture and the Lambda function are same. Lambda supports arm64 and x86_64 instruction set architectures.
When the Lambda deployment package doesn't have the correct security permissions, you receive a "permission denied" error along with the "Runtime.InvalidEntrypoint" error occurs. In Unix permissions symbolic notation (from Wikipedia), 644 is the correct permissions for all files within a Lambda deployment package. For folders within a deployment package, the correct permissions setting is 755. For more information, see How do I troubleshoot "permission denied" or "unable to import module" errors when uploading a Lambda deployment package?