Compute & EBS

Audit your EC2 and EBS footprint to eliminate costs from abandoned instances and data.

EC2 Instances

Long-Stopped Instances

AWS Doctor identifies instances that have been in a stopped state for more than 30 days.

• Reason: While you don’t pay for CPU/RAM when stopped, you are still paying for the attached EBS root volumes and any persistent storage.
• Action: Terminate or snapshot the data and delete.

Expiring Reserved Instances (RI)

Scans for active RIs scheduled to expire in the next 30 days or that have expired in the last 30 days.

• Reason: Expired RIs revert to expensive On-Demand pricing without warning.
• Action: Review usage and renew or migrate to Savings Plans.

EBS Volumes & Snapshots

Unused EBS Volumes

Finds volumes with a status of available (meaning they are not attached to any instance).

• Reason: You are billed for the provisioned size of these volumes every hour they exist.
• Action: Delete if no longer needed.

Orphaned Snapshots

Finds snapshots where the source volume has been deleted and the snapshot is not associated with any AMI.

• Reason: Often created during manual backups or old deployments and forgotten.
• Action: Delete to save on S3-backed storage costs.

Stale Snapshots & AMIs

Flags AMIs and snapshots that are older than 90 days and are not associated with any running or stopped instance.

• Reason: Outdated base images and backups that likely haven’t been touched in a quarter.
• Action: Clean up old versions of images.

Access & Security

Unused Key Pairs

Identifies EC2 Key Pairs that are not associated with any running or stopped instance.

• Reason: Reduces administrative clutter and potential security risks from old keys.
• Action: Delete unused keys from the console/CLI.