To transition an AWS Lambda function from a .zip package to a container image, the container image must be stored in Amazon Elastic Container Registry (ECR). The process involves creating an ECR repository in the same AWS Region as the function, packaging the function code into a container image using a Dockerfile, and pushing this image to the ECR repository. Finally, the existing Lambda function's configuration must be updated to change the package type from .zip to image and to specify the full ECR image URI, which includes the repository URI and a specific image tag or digest. Option A accurately describes this complete, standard procedure.

B: This is incorrect because Lambda container images must be stored in Amazon ECR, not Amazon S3. S3 is used for .zip file deployments and storing IaC templates.

C: This is incorrect for the same reason as option B. AWS CloudFormation requires the container image to be located in an Amazon ECR repository, not an S3 bucket.

D: This option is incomplete. Simply specifying the repository URI is insufficient. Lambda requires the full image URI, which must include a specific image tag or digest to identify the exact version to deploy.

1. AWS Lambda Developer Guide

"Deploying Lambda functions as container images": This document explicitly states

"You upload your container images to Amazon Elastic Container Registry (Amazon ECR)." It then outlines the workflow: create a repository

build the image

push to ECR

and then create or update the function to use the image URI. This supports the entire process described in option A.

2. AWS Lambda Developer Guide

"Creating Lambda functions defined as container images": Under the "Prerequisites" section

it lists

"A container image uploaded to an Amazon ECR repository in the same AWS Region as your function." This confirms the ECR and same-region requirements.

3. AWS CLI Command Reference

update-function-code: The documentation for this command shows the --image-uri parameter. The required format is ECR-URI:TAG (e.g.

123456789012.dkr.ecr.us-east-1.amazonaws.com/my-repo:my-tag)

demonstrating the necessity of including both the repository URI and a tag

which makes option A more complete than option D.