Recommendations are cheap. Shipping the fix is the work.
Every cost tool can produce a rightsizing list. The reason those lists rot in a dashboard is that turning one into a merged change means finding the resource in Terraform, editing the instance type, opening a PR, and getting it reviewed. nable closes that gap: it resolves each recommendation to the resource in your Terraform (from state), edits it, and opens the PR.
How it works
1. Find and price
nable reads utilization and flags over-provisioned EC2/RDS/ECS, priced on your real effective rate, not on-demand list.
2. Draft the change
It resolves each recommendation to the resource in your Terraform (from state or an override) and edits the instance type.
3. Open the PR
A pull request lands for you to review and merge. Prefer to keep your own git flow? A patch-only mode writes the files and leaves git to you.
# after `uvx nable`, connected to AWS + your infra repo
You: Open a rightsizing PR for the top savings
nable: data-worker-01 m5.4xlarge -> m5.2xlarge, saves $218/mo.
PR #142 drafted against your infra repo. Review and merge.Propose-only, always
nable never changes your cloud on its own. The rightsizing lands as a pull request a human approves, so you can wire it into your workflow without handing it write access to your account. It reads utilization and cost read-only.
Turn rightsizing from a list into a merged change. nable finds the waste, prices it on your real rates, and drafts the Terraform fix as a pull request you approve. Read-only, propose-only, runs on your machine. Free for solo use.
Common questions
Can nable open a pull request for AWS rightsizing?
Yes. nable finds over-provisioned EC2, RDS, and ECS, resolves each to the resource in your Terraform, edits the instance type, and opens a pull request you review and merge. It is propose-only and never changes your cloud directly.
Does it price on my real rates or list price?
On your real effective rate. nable prices the right-size against your negotiated and committed pricing, not on-demand list, so the saving is the one you would actually see on the invoice.
Do I have to let it change my infrastructure?
No. nable is read-only and propose-only. The fix is a pull request a human approves; there is also a patch-only mode that writes the files and leaves git and merging entirely to you.
What if my resources are not in Terraform?
nable resolves recommendations from Terraform state where available, and accepts a manual resource mapping as a fallback. The rightsizing analysis itself works regardless; the PR step needs a Terraform target.