Aws Lambda Managed Instances

This walks you through evaluating and migrating workloads to AWS Lambda Managed Instances, where your functions run on EC2 instances in your account while AWS handles the operational overhead. It's built around a practical routing system that sends you to the right reference doc based on what you need: cost comparison, instance sizing, thread safety reviews, migration patterns, or infrastructure setup. The quick decision table up front is genuinely useful. It saves you from chasing LMI when you have bursty traffic or need scale-to-zero economics. Best for steady, high-volume workloads above 50M requests per month where duration costs pile up and you can benefit from Savings Plans on the underlying EC2. Be ready to think about thread safety, especially if you're running Node.js, Java, or .NET.

skills.sh installs: 6.2K
GitHub stars: 3.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aws/agent-toolkit-for-aws --skill aws-lambda-managed-instances --agent claude-code

Installs into .claude/skills of the current project.

Files

AWS Lambda Managed Instances (LMI)

Runs Lambda Event Functions on EC2 instances in the user's account while AWS manages provisioning, patching, scaling, routing, and load balancing. Combines Lambda's developer experience with EC2's pricing and hardware options.

Works best with the AWS MCP server for sandboxed CLI execution and audit logging. All guidance also works with standard AWS CLI or SAM CLI.

Note: Confirm regional availability, quotas, and instance type offerings against current AWS documentation before production deployment.