aws-lambda-managed-instances

Evaluates, configures, and migrates Lambda workloads to AWS Lambda Managed Instances on EC2.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill aws-lambda-managed-instances-richardnroman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-lambda-managed-instances
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/aws-lambda-managed-instances
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill aws-lambda-managed-instances-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Deciding whether and how to move AWS Lambda functions to Lambda Managed Instances (LMI) requires cost analysis, concurrency safety review, capacity provider configuration, and infrastructure setup that is easy to get wrong. ## Core Features & Use Cases - Workload Assessment & Cost Comparison: Determines if LMI fits a workload based on traffic patterns, cold start tolerance, and runtime, with break-even guidance against standard Lambda pricing including Savings Plans. - Configuration & Infrastructure Setup: Provides instance family selection, memory-to-vCPU ratios, capacity provider scaling controls, IAM roles, VPC requirements, CLI commands, and SAM templates. - Migration & Troubleshooting: Supplies runtime-specific thread-safety checklists (Node.js, Java, .NET, Python), before/after code patterns, and diagnostics for throttling, stuck deployments, and cost anomalies. - Use Case: A team running a steady-traffic Node.js SQS processor at 80M requests per month uses this Skill to confirm LMI cost savings, configure a Graviton capacity provider, fix shared /tmp paths, and cut over gradually with weighted aliases. ## Quick Start Ask the assistant to evaluate whether your Lambda function is a good candidate for Lambda Managed Instances and to build a cost comparison and migration plan.

Frequently Asked Questions about aws-lambda-managed-instances

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a Lambda function to Lambda Managed Instances?▼

Assess traffic and cost fit, review code for concurrency safety, create a capacity provider with VPC config and an operator role, attach it to the function, publish a version, then shift traffic gradually with weighted aliases from 10% to 100%.

When is Lambda Managed Instances cheaper than standard Lambda?▼

LMI becomes cost-competitive at roughly 50-100M+ requests per month with steady, predictable traffic. It is not cheaper for low request volumes, sub-100ms functions, bursty traffic, or workloads needing scale-to-zero.

Does Python code need thread-safety changes for Lambda Managed Instances?▼

No. Python on LMI uses process-based isolation, so globals are not shared between invocations. The main concerns are shared /tmp file paths, per-process connection pools, and memory sizing multiplied by concurrency.

Why is my LMI capacity provider stuck in CREATING state?▼

The most common cause is private subnets missing a NAT gateway route, since instances need outbound internet access for image pulls and Lambda service communication. Also verify subnets span 3+ AZs and the operator role has required permissions.

What are the limits of Lambda Managed Instances?▼

Memory ranges from 2 GB to 32 GB, a minimum of 3 execution environments is required for AZ resiliency, instances rotate every 14 days, and concurrency per vCPU caps at 64 for Node.js, 32 for Java/.NET, and 16 for Python.