Savings Optimization Recommendations
Last updated
Was this helpful?
Last updated
Was this helpful?
Instances that have an average CPU consumption of less than 5% and network traffic below 1000 bytes/s for the last 7 days. We recommend terminating these instances to reduce expenses.
Images that haven't been used for a while might be subject to deletion, which would unlock the underlying snapshots. Image selection criteria:
The image creation date was more than 1 week ago.
No instances have been created from/related to this image in the past 7 days.
You can download the list of obsolete images as JSON for subsequent automated processing with the help of .
Redundant and old snapshots save up on storage expenses if deleted. You can download the list of snapshots as JSON for use in further implementations like clean-up scripts and maintenance procedures. Selection criteria:
The source EBS volume doesn't exist anymore.
No AMIs are created from this EBS snapshot.
It hasn't been used for volume creation for the last 4 days.
The list of obsolete snapshots can be downloaded as JSON for subsequent automated processing with the help of .
Obsolete IPs can be tracked for Azure and AWS clouds to reduce expenses. The following is the selection criteria for the obsolete IPs:
The IP was created more than 7 days ago.
The IP hasn't been used in the last 7 days.
It costs money to be kept.
Notification about volumes that haven't been attached for more than one day. These are considered to be forgotten or no longer relevant. We recommend that you delete such resources.
This recommendation is aimed at the detection of underutilized instances in AWS and Azure and suggests more suitable flavors for these machines. An instance is considered to be underutilized if:
It is active.
It exists for more than 3 days.
Its CPU metric average for the past 3 days is less than 80%.
This card contains instances that are active and have sustainable compute consumers for more than 90 days. Instances that haven't been covered with Reserved Instances or Saving Plans are also included.
For all such instances, consider purchasing Reserved Instances to save on compute usage. Check RI/SP Coverage to see the detailed breakdown of current reservations.
This card shows Kinesis Streams with provisioned Shard capacity that haven't performed operations in the last 7 days. Consider removing them to reduce expenses.
This card shows opportunities to migrate instances if the tool detects that the same instance type is cheaper in a geographically close region (within the same continent).
Some of your active instances might cost less in another nearby region with the same specifications. Consider migrating them to the recommended region to reduce expenses.
This recommendation means that some of your instances have an inactivity pattern that allows you to set up an on/off power schedule (average CPU consumption is less than 5% and network traffic below 1000 bytes/s for the last 14 days). Consider creating a power schedule to reduce expenses.
This list contains instances that:
Are running for the last 3 days.
Have existed for less than 6 hours.
Were not created as Spot (or Preemptible) Instances. Consider using Spot (Preemptible) Instances.
An underutilized instance is one average CPU consumption of less than 80% for the last 3 days. FinOps for Cloud detects such active RDS instances and lists them on the card. Consider switching to the recommended size from the same family to reduce expenses.
Some snapshot chains don't have source volumes or images created from their snapshots and have not been used for volume creation for the last 3 days. Consider their deletion to save on snapshot storage expenses.
The instances in the list are active and have been identified as sustained compute consumers (for more than 90 days) but are not covered by subscription or Savings Plans. Consider purchasing subscriptions to reduce computing costs.
Detection of inactive, non-deallocated machines that have not been running for more than 1 day and are still billed by the cloud.
Upgrade older generation instances to the latest generation within the same family.
A bucket is abandoned if the average data size is less than 1024 megabytes, the Tier1 request quantity is less than 100, and the GETrequest quantity is less than 2000 for the last 7 days.
We recommend that you delete it to reduce expenses. Change the check period and other parameters in the card's Settings.
You can download the list of unattached volumes as JSON for subsequent automated processing with the help of .
You can download the list of non-deallocated VMs as JSON for subsequent automated processing with the help of .
