Tutorials
Step-by-step AWS waste guides with validation steps, ROI framing, owner-ready findings, and accountability handoff.
Tutorials
Use this page as the index for the public AWS cost cleanup tutorials. Each guide is written for startup engineering teams that want concrete console steps, CLI commands, risk warnings, and a simple way to frame the savings.
On this page
- Featured guides
- Coverage against major supported finding types
- What these tutorials cover
- Best way to use this section
- After the first cleanup pass
Featured guides
- How to Find Unused NAT Gateways in AWS
- How to Reduce CloudWatch Logs Retention Safely
- How to Audit EBS Waste Across Regions
- How to Create the OpsCurb Core Scan Role
Coverage against major supported finding types
The following SEO-focused finding pages now exist for major scan categories:
- Idle RDS instances
- Unattached EBS volumes
- gp2 to gp3 cost savings
- NAT gateway to S3 endpoint savings
- CloudWatch log retention cost
- Unused Elastic IPs
- Stopped EC2 instances
- Idle load balancers
- Stale RDS snapshots
- Stale EBS snapshots
- Empty S3 buckets
- Stale ECR repositories
- Unused IAM credentials
What these tutorials cover
- Console paths and CLI commands for the AWS cleanup work you can validate today
- Risk warnings before you stop, delete, reroute, or shorten retention on live infrastructure
- Lightweight ROI framing so the cleanup can compete for engineering time
- Links back to Pricing, the Sample First-Scan Report, and the Free Review when you want help operationalizing the work
Best way to use this section
- Start with the guide that matches the waste pattern already visible in your account.
- Validate ownership and dependencies before any destructive action.
- Snapshot or document rollback posture where the recovery value matters.
- Turn the output into a short queue with named owners and expected monthly savings.
After the first cleanup pass
If the main challenge is not finding one issue but keeping savings work visible every month, connect an account with the Core Scan Role first and compare the live findings to the same categories covered here. That is where OpsCurb is designed to help: recurring scans, prioritized findings, owner tracking, and a first-scan brief that can be forwarded internally.
Questions? Email support@opscurb.com.