Parsivex scans your AWS account for 13 types of waste. Each finding type below links to a dedicated article explaining what triggers the flag, how to fix it, and typical savings ranges.
Titles and short descriptions match what you see on finding cards in your scan reports.
Compute
| Finding type | What it means |
|---|---|
| Idle EC2 instance | An EC2 instance with very low CPU utilization that can be stopped or terminated. |
| Over-provisioned Lambda memory | A Lambda function allocated more memory than its invocation metrics justify. |
| Oversized EC2 instance | An EC2 instance running on a larger instance type than its workload requires. |
| Reserved Instance opportunity | Stable compute usage that could save money with Reserved Instance or Savings Plan pricing. |
Storage
| Finding type | What it means |
|---|---|
| Incomplete multipart uploads | Aborted S3 multipart uploads still consuming storage with no lifecycle rule to clean them up. |
| Orphaned EBS snapshot | An EBS snapshot with no associated volume or AMI still incurring storage charges. |
| Orphaned EBS volume | An unattached EBS volume still incurring storage charges. |
| S3 wrong storage class | An S3 bucket without lifecycle rules to transition infrequently accessed objects to cheaper tiers. |
Database
| Finding type | What it means |
|---|---|
| Over-provisioned DynamoDB capacity | A DynamoDB table on provisioned billing whose consumed capacity is a small fraction of what is provisioned. |
| Over-provisioned RDS instance | An RDS database running on a larger instance class than its workload requires. |
Networking
| Finding type | What it means |
|---|---|
| NAT Gateway overuse | High NAT Gateway data-processing charges that could be reduced with VPC endpoints. |
| Unused Elastic IP | An allocated Elastic IP address not associated with a running instance. |
Compute & networking
| Finding type | What it means |
|---|---|
| Idle load balancer | A load balancer with no healthy targets or near-zero traffic still incurring hourly charges. |