AWS Lambda now supports running event‑driven functions on EC2 G‑series GPU instances via the Lambda Managed Instances feature. The change introduces up to 48 concurrent invocations that share one model per GPU, leverages vLLM and SGLang base images that require no custom handler code, and raises the asynchronous timeout limit to 90 minutes.
GPU Model Sharing Mechanics
Each G‑series GPU can host a single model image while allowing 48 Lambda invocations to execute against it simultaneously. The shared‑model approach reduces per‑invocation cold‑start overhead and can improve overall throughput for batch‑style inference workloads.
Operational Impact
Billing combines the underlying EC2 instance price with an additional 9.75 percent fee. Early tests note an eight‑minute publish step and the absence of response streaming, which may affect latency expectations for interactive use cases. The extended 90‑minute timeout enables longer processing pipelines that were previously impossible in the standard Lambda runtime.
Implementation Considerations
Developers can start from the provided vLLM or SGLang base images, eliminating the need to write a Lambda handler. The model must be baked into the image or made available to the instance at launch. Concurrency is capped at 48 per GPU, so capacity planning should account for the number of GPUs required to meet peak demand.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
- Evaluate whether your inference workload fits the batch or long‑running pattern that benefits from 90‑minute execution windows.
- Plan GPU allocation based on the 48‑invocation sharing limit to avoid over‑committing a single GPU.
- Incorporate the 9.75 % fee into cost models alongside the underlying EC2 pricing.
- Test the eight‑minute publish time in your CI pipeline to ensure deployment pipelines remain within acceptable windows.
- Review existing security and IAM policies for Lambda Managed Instances, as they now govern access to EC2 GPU resources.

