You suspect lots of resources do nothing yet cost
Stopped EC2 doesn't cost compute, but EBS volumes do. Idle is broader than stopped.
Try this first
- 1Identify EBS volumes in 'available' state (unattached), they cost
- 2Find RDS with 0 connections in the last 7 days
- 3Unattached old EIPs cost per hour
- 4Test/dev that doesn't stop after hours, schedule via Lambda or Automation
When to bring us in
Tools like Cost Optimizer, Trusted Advisor (Business Support) or third parties give dashboards.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.