AWS Lambda now logs managed EC2 instance lifecycle events
Lambda Managed Instances capacity providers automatically publish structured JSON logs to CloudWatch, giving operators visibility into scaling and provisioning activity.
Does AWS Lambda now log scaling activity for managed EC2 instances?
Yes. As of July 24, 2026, AWS Lambda automatically publishes logs for Lambda Managed Instances (LMI) capacity providers to Amazon CloudWatch Logs. The logs are structured JSON and cover instance lifecycle events, giving teams a direct way to diagnose provisioning failures and understand scaling behavior without additional instrumentation.
What is Lambda Managed Instances?
LMI lets you run Lambda functions on EC2 instances while keeping the operational model serverless. You define compute resources through capacity providers, and Lambda handles provisioning on your behalf. The typical use case is high-volume, predictable workloads that benefit from specialized compute configurations or EC2 pricing options such as Savings Plans and Reserved Instances.
What exactly gets logged?
Lambda generates structured JSON log entries for three categories of capacity provider events: instance launches, instance terminations, and health checks. Because the format is structured, you can use CloudWatch Logs filtering and querying to isolate failed operations or provisioning errors without parsing free-form text.
Logs are enabled by default for every capacity provider; there is no opt-in step required. You can view them directly from the Lambda console's capacity provider page.
How do you change the log configuration?
If you need to adjust log settings, AWS supports several management paths:
- Lambda console — capacity provider page
- Lambda API
- AWS CLI
- AWS SAM
- AWS CloudFormation
The flexibility means teams that manage infrastructure as code can version-control their log configuration alongside the rest of their Lambda setup.
Availability and pricing
| Detail | Value |
|---|---|
| Enabled by default | Yes, for all capacity providers |
| Log format | Structured JSON |
| Destination | Amazon CloudWatch Logs |
| Regional availability | All AWS Commercial Regions where LMI is available |
| Additional Lambda charges | None stated |
| CloudWatch charges | Standard CloudWatch Logs rates apply |
The only cost consideration AWS calls out is standard CloudWatch Logs pricing. Because logs are on by default, teams running LMI at scale should account for log ingestion and storage volume when reviewing CloudWatch spend.
Why this matters for operators
Before this change, diagnosing why a capacity provider failed to launch an instance or why scaling behaved unexpectedly required working around the absence of native lifecycle visibility. Structured logs delivered automatically to CloudWatch close that gap and integrate with existing alerting and observability pipelines that already consume CloudWatch data.
For teams already using CloudWatch Logs Insights or metric filters, the structured JSON format means they can build dashboards or alarms on specific event types, such as repeated termination events, without custom log parsing logic.