Deploy Docker Image to AWS Lambda Without Using ECR

Unfortunately, AWS Lambda with container image package type requires the container image to be stored in Amazon ECR (Elastic Container Registry). There is currently no direct support for deploying container images to Lambda from third-party container registries like JFrog Artifactory.

When deploying Lambda functions using container images, the workflow typically involves:

1. Building your Docker image locally
2. Tagging the image with your ECR repository URI
3. Pushing the image to Amazon ECR
4. Creating or updating your Lambda function to use that ECR image

The Lambda service needs to be able to access and pull the container image, which is why it's tightly integrated with ECR. This integration ensures proper permissions and accessibility for the Lambda service.

If you must use JFrog Artifactory, you would need to implement a workflow that:

1. Stores your container image in JFrog Artifactory
2. Pulls the image from Artifactory during your deployment process
3. Pushes it to ECR
4. Then deploys to Lambda

This intermediate step of moving the image from Artifactory to ECR would be necessary as Lambda cannot directly pull from external registries.

For container-based Lambda functions, the ECR requirement is a constraint of the service design, and there are currently no supported alternatives for hosting the container images outside of ECR.
Sources
Deploy Go Lambda functions with container images - AWS Lambda
Deploy Lambda functions with container images - AWS Prescriptive Guidance