AWS deprecation migration tools · MIT-licensed · 116 tests passing

Every AWS deprecation deadline
deserves a kit.

Surgical, single-command migration tools for Lambda runtimes, Amazon Linux, and other AWS platform deprecations. Scan your account. Codemod your code. Patch your IaC. Deploy canary with auto-rollback. Ship before the deadline.

lambda-lifeline live demo — scan, codemod, audit, iac, plan
lambda-lifeline live demo · click for al2023-gate or python-pivot

Three live kits. Three live deadlines.

Each kit targets one AWS deprecation with one coherent CLI. Works offline for demos and CI. No AWS creds required to try.

Deadline: 2026-04-30 · 2 days

lambda-lifeline

Lambda Node.js 20 → 22

Scan all Node Lambdas. Rewrite import assertimport with. Audit native bindings (sharp, bcrypt, canvas). Patch SAM, CDK, Terraform, Serverless. Canary deploy with CloudWatch-alarm auto-rollback.

  • 8 CLI commands · 24 tests passing
  • Node.js 20 LTS · MIT licensed
  • SAM + CDK + Terraform + Serverless
Read the docs →
Deadline: 2026-06-30 · 63 days

al2023-gate

Amazon Linux 2 → AL2023

Scan EC2, launch templates, EKS node groups, ECS task defs, Beanstalk for AL2. Translate yum packages to dnf with a 50-package curated table. Generate Packer template, diff cloud-init, patch Ansible. Migration runbooks for ASG / EKS / ECS / EB.

  • 6 CLI commands · 48 tests passing
  • Python 3.9+ · zero runtime deps
  • Packer HCL + Ansible patcher
Read the docs →
Deadline: 2026-10-31 · 186 days

python-pivot

Lambda Python 3.9/3.10/3.11 → 3.12

Scan Python Lambdas by severity and days-to-EOL. Codemod collections.abc, distutils, asyncio, datetime.utcnow(). Audit requirements.txt for cp312 wheel availability (30+ package table). Patch IaC. Canary deploy + rollback.

  • 6 CLI commands · 44 tests passing
  • Python 3.9+ · zero runtime deps
  • boto3 optional for live scan
Read the docs →

How every kit works

One consistent shape across all three: scan → fix → test → deploy → rollback. Pick any step. Skip any step. Re-run any step.

1

Scan

Read-only API calls find every resource on the deprecated runtime. Output as table / JSON / CSV / Markdown. Fixture mode works offline.

2

Fix

Narrow, mechanically-safe code rewrites. Everything ambiguous is flagged for human review, not auto-changed. Always dry-run by default.

3

Test

Native test suite on every kit (node --test / pytest). 116 tests total. Every command, every format, every exit code.

4

Deploy

Staged canary: 5% → 25% → 50% → 100%. Every stage checks a CloudWatch alarm. Trip = instant auto-rollback.

5

Rollback

Tested rollback path on every kit. Alias re-point for Lambda. Launch Template revert for EC2. Blue/green node-group swap for EKS.

Pricing

The CLIs are MIT-licensed — fork, use, resell. Paid tiers handle the parts that matter to a busy team: hash-anchored audit reports, real PRs opened on your repo, org-wide licenses, and continuous drift monitoring.

CLI (Free)

$0
  • All three kits, MIT licensed
  • Unlimited runs, no limits
  • Full source on GitHub
  • Community support via GitHub Discussions
git clone →

Migration Pack

$1,499
  • Real PR opened on your repo
  • Codemods + IaC patches
  • Canary plan + rollback script
  • Refund auto-fires if CI fails
Get Migration Pack →

Enterprise Options

Org License · $14,999/yr — live rule-pack feed, private rules, unlimited runs
Drift Watch · $19/mo — weekly re-scan, delta PDFs, auto-PR on new deprecations
Contact for Enterprise →

FAQ

Are the kits actually free?

Yes. Every line of code on GitHub is MIT. You can run the CLI, scan your account, codemod your code, patch your IaC, and deploy without paying us a cent. Paid tiers only add the docs/videos/consulting around the kits.

How is this different from CloudQuery / AWS Migration Hub / custom scripts?

CloudQuery gives you the inventory. We give you the inventory plus the codemod plus the IaC patch plus the staged deploy plus the tested rollback — scoped to one specific deprecation. AWS Migration Hub is for lift-and-shift between regions/accounts, not runtime upgrades. Custom scripts exist, but nobody has tested-end-to-end-with-rollback custom scripts for these exact deadlines.

Will the codemods break my code?

They're designed not to. Every kit rewrites only the narrow, mechanically-safe patterns (like import assertimport with) and lints everything ambiguous so you decide. Every kit defaults to dry-run. Every apply has a dry-run preview first. And every kit ships with a full test suite covering both modes.

What if the canary deploy fails?

That's the point. Every kit's deploy command requires a CloudWatch alarm ARN with --apply. At every canary stage it checks the alarm state. If the alarm is in ALARM state, it instantly reverts the alias to the previous stable version and exits non-zero. You get rollback whether you wanted one or not.

What's the company behind this?

A small independent shop. No VC. No pivot. We ship one kit per deadline. If we can't ship it at kit quality in one week, it doesn't ship.

Which kit should I buy first?

The one whose deadline is closest. If you're running Lambda on Node 20, start with lambda-lifeline — deadline 2026-04-30. Running EC2 on Amazon Linux 2? al2023-gate, deadline 2026-06-30. Running Python Lambdas? python-pivot. Running all three? Bundle.

Do you offer refunds?

Yes. Migration Pack purchases auto-refund if the opened PR's CI fails within 7 days. Audit PDFs include a verification URL to confirm authenticity.