This recommendation identifies EBS instances that are active, but no longer attached to any instance.

Identify EBS instances that are active, but no longer attached to any instance for the last x days (subject to preferences).

1. Days To Check, default 7 days.

Umbrella.

No.

This recommendation identifies which EBS types should be adjusted to optimize costs while meeting performance requirements.

1. Based on the usage in the past 14 days (subject to preferences).

2. The recommendation is applicable when saving >5%.

3. We recommend transitioning to more cost-efficient and performance-optimized EBS volume types:

• Move from io1 to gp3: Gain equivalent or better performance at a lower cost, with flexible provisioning of IOPS and throughput tailored to your workload needs.

• Move from gp2 to gp3: Reduce costs by approximately 20% while benefiting from consistent baseline performance and the ability to customize IOPS and throughput independently of storage size.

Note: that in contrast to the other recommendations, the chart displayed for this service is called IOPS PERFORMANCE. An additional chart called THROUGHPUT PERFORMANCE is shown with the following metrics:

• Max Read Throughput
• Max Write Throughput
• Actual Read Throughput
• Actual Write Throughput

1. Min Potintial Savings.
2. Days To Check.

Umbrella.

Yes.

This recommendation identifies outdated EBS snapshots that can be deleted to reduce costs.

• Identify EBS outdated Snapshot age that is more than 21 days (subject to preferences).

  • Identify snapshots that have high (costs ±42$ per year) and is not connected to any image.

  1. Retrieve the existing snapshot date from the API.
  2. Validate that there's not connected to any existing AMI at this point
  3. Retrieve the average daily cost.
  4. Multiply the average daily cost by the number of days that the snapshot exists until the recommendation creation.

1. Min Annual Cost, default $3.5.
2. Days Back= Days to Check, default 21 days.

Umbrella.

No.

This recommendation identifies EBS snapshots created for AMIs that are no longer in use.

An “orphaned AMI” means that the AMI itself has been deleted, but its associated snapshots still remain, incurring ongoing storage costs without serving any active purpose.

1. Retrieve the existing snapshot date from the API.
2. Identify snapshots that have high (costs ±42$ per year) and is not connected to any image.
3. Validate that there's not connected to any existing volume at this point.
4. Retrieve the average daily cost.
   5.Multiply the average daily cost by the number of days that the snapshot exists until the recommendation creation.

1. Min Annual Cost, default $3.5.
2. Days Back= Days to Check, default 21 days.

Umbrella.

No.