Skip to content

Sync LMI power with upstream skill accuracy corrections#139

Open
sbbhimji wants to merge 1 commit into
kirodotdev:mainfrom
sbbhimji:update-lmi-power-accuracy
Open

Sync LMI power with upstream skill accuracy corrections#139
sbbhimji wants to merge 1 commit into
kirodotdev:mainfrom
sbbhimji:update-lmi-power-accuracy

Conversation

@sbbhimji
Copy link
Copy Markdown
Contributor

Summary

Syncs the AWS Lambda Managed Instances power with recent accuracy corrections made to the source LMI skill (reviewer feedback on the upstream Claude Code plugin).

Changes

  • Clarify execution environments vs EC2 instances (drop fixed 3-instance and undocumented 14-day claims)
  • MaxVCpuCount defaults to 400 (not required); MinExecutionEnvironments min 1 non-prod, 3+ recommended for prod AZ coverage
  • Instance family minimums: C .xlarge+, M/R .large+ (~450 types)
  • Cost threshold reframed to ~$1,000/month Lambda spend; scaling 'doubles within 5 min without throttles'
  • Soften VPC subnet requirement (min 1, 3+ recommended); VPC endpoints only needed without NAT
  • Add /tmp usage estimation to migration and thread-safety checklists
  • Add instance (~12h) and execution environment (~4h) lifespans; add regional availability list

Files

POWER.md and 5 steering files (configuration-guide, cost-comparison, infrastructure-setup, thread-safety, troubleshooting).

Testing

Content-only update; verified via grep that all corrected values are present and stale values removed.

Apply recent corrections from the source LMI skill:
- Clarify execution environments vs EC2 instances (drop fixed 3-instance/14-day claims)
- MaxVCpuCount defaults to 400 (not required); MinExecutionEnvironments min 1 non-prod, 3+ prod
- Instance family minimums: C .xlarge+, M/R .large+ (~450 types)
- Cost threshold ~$1,000/month Lambda spend; scaling doubles within 5 min without throttles
- Soften VPC subnet requirement (min 1, 3+ recommended); VPC endpoints only if no NAT
- Add /tmp usage estimation to migration/thread-safety checklists
- Add instance (~12h) and execution environment (~4h) lifespans; regional availability list
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant