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
Ops choosing how a new court-document Lambda should ship should pick zip-from-S3 for simpler dependency sets within size limits, or container images from ECR when the runtime needs custom OS packages or larger packaged environments. Lambda supports both ZIP archives and container images; the distinction is packaging needs for the release train, not myths that one option is mandatory. Municipal court-document processors with heavy native libraries often justify images; simple handlers stay on zip.
Claiming Lambda can only deploy from EC2 AMIs so neither zip nor ECR images apply fails factually—AMIs are not the Lambda deployment unit. Claiming container images are required for every Lambda because zip packages are deprecated for all runtimes fails conceptually; zip remains valid within constraints. Treating zip and ECR images as interchangeable cosmetics with identical operational constraints fails because size, cold start, and tooling differ.
Exam caveat: whichever form you choose must still be built for the target architecture and scanned/promoted through the same CI gates. Operational check: inventory dependencies for the court-document function, choose zip or image accordingly, deploy to a test function, and confirm import and runtime behavior before the release train proceeds.