AWS re:Invent 2025: Lambda Managed Instances Bring EC2 Flexibility to Serverless
What is AWS re:Invent?
AWS re:Invent is Amazon Web Services’ largest annual cloud conference, where AWS announces new services, enhancements, and strategic direction for the coming year. The event features keynotes, technical deep dives, hands-on sessions, and hundreds of product launches, making it one of the most influential cloud events in the industry.
AWS opened re:Invent 2025 with a significant update to its compute portfolio: Lambda Managed Instances. This new capability lets Lambda functions run on managed EC2 instances, preserving the serverless operational model while enabling access to specialized hardware, predictable pricing models, and steady-state cost optimization.
For many teams, this removes a long-standing tradeoff: choosing between Lambda’s simplicity and EC2’s flexibility.
What AWS Announced
Lambda Managed Instances allow you to attach Lambda functions to a capacity provider, which represents a managed pool of EC2 instances. Users specify:
• Instance types (or include all for broad coverage)
• VPC, subnets, and security groups
• Scaling parameters such as max vCPUs or CPU-based policies
AWS then handles everything operational: instance provisioning, OS patching, security updates, load balancing, and scaling. Instances rotate on a 14-day schedule, and Lambda routes requests directly to pre-provisioned environments to avoid cold starts.
The feature also supports multiconcurrency, meaning one execution environment can process multiple requests at once. This allows better resource sharing and reduces the number of environments required to handle traffic.
Pricing Model
Lambda Managed Instances introduces three cost components:
1. Standard Lambda invocation charges
2. Standard EC2 instance charges (with full support for Reserved Instances and Compute Savings Plans)
3. A 15% management fee based on the EC2 on-demand price
Because compute is tied to EC2 rather than per-invocation duration, there are no duration-based Lambda charges. For consistent or always-on workloads, this can make the model significantly more cost-efficient.
Why This Matters for AWS Users
1. More Workloads Can Stay in the Lambda Model
Organizations that previously had to move off Lambda to achieve specialized compute or lower costs may now stay serverless while gaining access to the latest generation of EC2 hardware, including Graviton4.
2. A New Middle Ground Between Serverless and EC2
Lambda Managed Instances occupies a space between event-driven Lambda and fully managed EC2 fleets. Teams retain serverless operations, no servers to patch or scale, while customizing compute characteristics.
3. Better Fit for Steady or Predictably Scaling Applications
Multiconcurrency, paired with EC2-based capacity and long-term pricing models, supports workloads with stable traffic patterns or cost sensitivity.
4. Some Code May Require Changes
Because multiple requests may run within the same execution environment, teams need to ensure code does not rely on shared state that could cause concurrency issues. This is one of the key considerations before migrating existing functions.
How It Scales
When demand increases, AWS adds new EC2 instances to the capacity provider within seconds. The system absorbs up to a 50% traffic increase without scaling, and built-in circuit breakers throttle requests only when the provider has reached its maximum capacity during extreme surges.
All monitoring, permissions, and deployment workflows remain the same as with standard Lambda. The initial release supports Node.js, Python, Java, and .NET.
Who Might Benefit Most
Lambda Managed Instances could be especially valuable for:
• High-traffic applications with predictable load
• Data-intensive or network-heavy workloads
• Teams adopting newer architectures like Graviton4
• Applications where Savings Plans or RIs deliver meaningful cost reductions
• Workloads that outgrow traditional concurrency models
It won’t replace standard Lambda or EC2, but it provides a strong new option in the compute spectrum.
A Meaningful Expansion of Serverless
This launch redefines what “serverless” can mean in practice. Instead of tying serverless to a particular execution engine, AWS is turning it into an operational contract: AWS handles the infrastructure, regardless of what that infrastructure is.
Lambda Managed Instances broadens the range of applications that can use Lambda patterns without giving up compute flexibility or cost control. As it matures, it may significantly influence how organizations design and operate cloud-native workloads.
Official Sources
AWS Lambda Developer Guide https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
Forged Concepts
Explore expert cloud, AWS, and DevOps insights by forged Concepts, a trusted AWS MSP
View All Posts →