A Lambda that preprocesses large GIS libraries for a parks department exceeds practical zip size and dependency constraints. Which packaging guidance should the team apply?
Select an answer to reveal the explanation.
Short Explanation
Tiny zip, huge GIS stack—pick the box that fits. Lambda container images handle fat preprocessing deps; zip stays great for lean handlers. Crowbar-fitting libraries into mapping templates or pretending Lambda has no image option misses the packaging menu.
Full Explanation
Lambda supports both zip deployment packages and container images. Container images are appropriate when dependency trees are large or need custom OS libraries, while zip remains suitable for smaller footprints within documented size limits. Knowing that tradeoff is part of preparing application artifacts. EC2 user-data and API Gateway templates are not Lambda packaging substitutes for heavy GIS preprocessing.