- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add awslabs/agent-plugins --skill aws-lambda-managed-instances -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add awslabs/agent-plugins --skill aws-lambda-managed-instances -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add awslabs/agent-plugins --skill aws-lambda-managed-instances -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add awslabs/agent-plugins --skill aws-lambda-managed-instances -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/awslabs/agent-plugins/tree/HEAD/plugins/aws-serverless/skills/aws-lambda-managed-instances公開元より
Run Lambda functions on current-generation EC2 instances in your account while AWS manages provisioning, patching, scaling, routing, and load balancing. Combines Lambda's developer experience with EC2's pricing and hardware options.
For standard Lambda development, see aws-lambda skill. For SAM/CDK deployment, see aws-serverless-deployment skill.
Gather these signals before recommending:
/tmp paths? Per-invocation DB connections?If Lambda Insights is enabled on the function, use these metrics to calculate your starting configuration. If Lambda Insights is not enabled, suggest adding it to gather accurate workload data — but only proceed with the user's explicit confirmation, as adding the Insights layer may affect function performance or cold start times.
To check if Lambda Insights is enabled, look for a LambdaInsightsExtension layer on the function. To add it, find the latest layer ARN for your region from the Lambda Insights documentation and attach the CloudWatchLambdaInsightsExecutionRolePolicy managed policy to the function's execution role.
Target max concurrency (from cpu_total_time and Duration):
PerExecutionEnvironmentMaxConcurrency = floor((0.5 × Duration) / cpu_total_time)
This targets 50% CPU utilization at full concurrency, leaving headroom for scaling.
Memory allocation (from memory_utilization and current memory):
MemorySize = min(32768, max(2048, MaxConcurrency × (memory_utilization / 100) × current_allocated_memory))
This overestimates (assumes no shared base memory) but provides a safe starting point. The outer min caps the result at the 32 GB (32768 MB) LMI maximum.
Minimum execution environments (from baseline ConcurrentExecutions):
MinExecutionEnvironments = max(3, ceil(baseline_concurrent_executions × 2 / MaxConcurrency))
Targets 50% concurrency utilization to leave headroom for traffic bursts.
Without Lambda Insights: Start with the runtime's default max concurrency, 2 GB memory, and MinExecutionEnvironments = 3. Adjust during testing.
REQUIRED: Present a cost comparison before recommending LMI. Compare at minimum:
Rule of thumb: LMI becomes cost-competitive when your Lambda spend exceeds ~$1,000/month with steady traffic.
For discount analysis (Savings Plans, Reserved Instances), refer users to the AWS Pricing Calculator and references/cost-comparison.md for formulas and worked examples. Discount recommendations require workload-specific forecasting beyond this skill's scope.
Instance families (~450 types): C-series (compute, .xlarge+), M-series (general, .large+), R-series (memory, .large+). ARM (Graviton) for best price-performance.
Memory-to-vCPU ratios: 2:1 (default, CPU-bound work), 4:1 (general/mixed workloads), 8:1 (memory-heavy or Python apps). Min 2 GB, max 32 GB.
Multi-concurrency defaults/vCPU: Node.js 64, Java 32, .NET 32, Python 16.
Scaling: MinExecutionEnvironments (default 3), MaxVCpuCount (default 400), TargetResourceUtilization.
Scheduled scaling: For predictable traffic (business hours, marketing events), use EventBridge Scheduler to adjust Min/Max execution environments on a one-time or recurring schedule — scale up before peak, scale down or to zero when idle.
See references/configuration-guide.md for decision trees and detailed tuning.
Review code for concurrency safety. LMI runs multiple invocations concurrently per execution environment, but the model differs by runtime:
/tmp conflicts and memory sizing (per-process × concurrency).Common issues (all runtimes): shared /tmp paths, per-invocation DB connections.
Thread-safety issues (Node.js/Java/.NET only): mutable globals, non-thread-safe libs.
See references/thread-safety.md for the review checklist and references/migration-patterns.md for runtime-specific before/after code.
See references/infrastructure-setup.md for CLI commands and SAM templates.
/tmp and memory for Python)/tmp usage under max concurrency/tmp paths without request-unique namingSee references/troubleshooting.md for detailed resolution steps.
REQUIRED: AWS credentials configured on the host machine.
Verify access: Run aws sts get-caller-identity
Available in all commercial AWS Regions except Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), and Asia Pacific (Auckland).
Check the Lambda Managed Instances documentation for the latest regional availability.
Default: TypeScript
Override: "use Python" → Python, "use JavaScript" → JavaScript. When not specified, ALWAYS use TypeScript.
Default: CDK
Override: "use SAM" → SAM YAML, "use CloudFormation" → CloudFormation YAML. When not specified, ALWAYS use CDK.
>
---name: aws-lambda-managed-instancesdescription: >---# plugins/aws-serverless/skills/aws-lambda-managed-instances/SKILL.mdよくある質問
公開元から plugins/aws-serverless/skills/aws-lambda-managed-instances/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/awslabs/agent-plugins で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。