Use case
Tier cold storage and upgrade to gp3
Move rarely-touched data to cheaper tiers, upgrade EBS and RDS volumes from gp2 to gp3 in place, and clear stale snapshots — with the exact targets.
eks · prod-workers
$4,800/mo
High
rds · analytics-staging
$1,180/mo
Medium
ecs · checkout-api
$640/mo
High
ec2 · 14 × gp3
$312/mo
High
The problem
Storage costs creep. Hot and cold data sit on the same expensive tier, EBS and RDS volumes stay on older gp2 long after gp3 became the cheaper default, and snapshots pile up with nothing referencing them. None of it shows up as a single scary line on the bill.
How Lizrd fixes it
Lizrd reads your storage footprint and metadata read-only and surfaces the concrete moves: volumes to upgrade from gp2 to gp3 (cheaper per GB with a higher performance floor, applied in place with no downtime), data to shift to a colder tier, and orphaned snapshots that are safe to remove — each with the evidence and the exact change.
The outcome
Lower storage spend without touching a running workload’s performance. Every change is reversible, and the realized saving is confirmed on the next sync.
“The gp2-to-gp3 upgrades alone paid for the quarter. Same performance, applied in place, no downtime — Lizrd just listed every volume that qualified.”
More ways to save
Cover steady usage with commitments
Savings Plans and committed-use discounts are free money on steady baselines — if you size them right. Lizrd finds your safe, always-on floor to commit against.
Cut idle networking waste
Idle NAT gateways, unattached elastic IPs, and load balancers with no traffic bill around the clock. Lizrd finds them and confirms what's safe to remove.
Delete orphaned resources
Unattached volumes, unused IPs, and stale snapshots keep billing with nothing using them. Lizrd finds them and confirms they're safe to remove.
Find this in your own cloud
Connect read-only and Lizrd surfaces the highest-impact fixes — with the exact change to make.