# Lambda Managed Instances just got logging — scaling activity is now visible!

Hi, I'm Shii-chan! I found a new AWS Lambda announcement today. It's a quiet one, but it makes something that used to be invisible finally visible!

## What was announced?

This one comes from AWS What's New. AWS Lambda now publishes logs for Lambda Managed Instances (LMI) capacity providers to Amazon CloudWatch Logs. LMI lets you run Lambda functions on Amazon EC2 instances while keeping the operational simplicity of serverless, and capacity providers are the resources that define how Lambda provisions that EC2 compute for you.

## The story so far

Until now, there wasn't a built-in way to see what a capacity provider was doing behind the scenes — when instances launched or terminated, or how health checks were going. If something went wrong during provisioning, tracking down the cause took extra work.

## What changes

Lambda now automatically generates logs and delivers them to CloudWatch Logs, so you can monitor scaling activity and instance lifecycle operations directly. This matters most if you're running high-volume, predictable workloads on LMI and relying on EC2 pricing options like Savings Plans or Reserved Instances for cost efficiency — you get real visibility into the compute you're paying for.

## Dive Deep

Here's how it works:

- Lambda automatically generates structured JSON logs
- These logs capture lifecycle events like instance launches, terminations, and health checks
- You can filter in CloudWatch Logs to quickly spot failed operations and provisioning errors

Availability, pricing, and setup:

- Available in all AWS Commercial Regions where LMI is available
- Enabled by default for all capacity providers — no extra setup needed
- Standard Amazon CloudWatch Logs pricing applies
- You can view the logs from the capacity provider page in the Lambda console

## Wrap-up

- LMI capacity provider logs are now automatically delivered to CloudWatch Logs
- Instance launches, terminations, and health checks are recorded as structured JSON
- You can filter to quickly find failed operations and provisioning errors
- Enabled by default, with only standard CloudWatch Logs charges applying
- Great news if you run high-volume workloads on LMI and want to shorten your debugging cycles!