Ops asks whether a new court-document Lambda for this release train should ship as a zip artifact from S3 or as a container image from Amazon ECR. What distinction should guide the choice?
Select an answer to reveal the explanation.
Short Explanation
Zip is the carry-on bag; the container image is checked luggage for odd-sized tools. Stay zip when deps fit; move to ECR when you need custom OS bits or a bigger boxed runtime. It is not AMI land and zip is not dead.
Full Explanation
Lambda supports deployment packages as ZIP archives (often stored in S3) and as container images from Amazon ECR. ZIP fits many language runtimes within package-size and dependency constraints; container images help when custom system libraries or larger environments are required. Developers should pick based on packaging needs for the release train, not myths that one option is mandatory or that AMIs are the Lambda unit of deploy.