This work is licensed under CC BY 4.0 - Read how use or adaptation requires attribution

Filter:

Loading...

Events

Loading...
Get Certified Join the Community
Take the State of FinOps 2025 Survey

Usage Optimization Opportunities

This asset focuses on providing a collection of resources to help identify types of cloud cost waste by service provider, including links to additional tools.

You can sort each card by Cloud Provider or Saving Potential. Each card includes User Stories by FinOps Practitioners, Playbooks, documentation, or code examples.

We want to thank all our contributors for their hard work on this asset over the years.

Related FinOps Capabilities
Workload Optimization
Did you find this useful?

Cloud Provider

Relative Savings

Service Category

Relative Effort

Risk

Aged Snapshots

Storage – Waste

Manually look in Azure portal at a list of all snapshots across all subscriptions you have read access to.

AMI Snapshots

Storage – Waste

Snapshots created from AMIs that are no longer available. These are no longer being used and so can be removed.

AWS S3 - Multipart Uploads

Storage – Waste

AWS Storage Lens or your dedicated Technical Account Manager can identify MPU’s in S3 buckets. Once you identity MPU’s on specific buckets, you can configure a lifecycle rule for those S3 buckets to automatically abort 7-day old (or whatever time period you find appropriate) incomplete multipart uploads. I’d argue that lifecycle rules on S3 buckets should be the default, not the exception. A full description of the services and outline of this process can be found in the AWS blog post here.

Azure SQL Database & SQL Managed Instance

Database – Waste

You can exchange your existing licenses for discounted rates on Azure SQL Database and Azure SQL Managed Instance. Save up to 30%. For new databases, during creation, select Configure database on the Basics tab and select the option to Save Money. For existing databases, select Compute + Storage in the Settings menu and select the option to Save Money.

Azure SQL Database Serverless Tier for Non-Production Workloads

Database – Waste

Save database costs by configuring serverless-tier (instead of provisioned compute option) for Non-Production workloads. Configure Auto-pause to save Azure costs.

BigQuery Capacity Commitments

BigQuery – Waste

Failure to purchase org level capacity commitments for BigQuery can result in runaway costs due to on-demand query costs. Purchasing an org level capacity commitment and enabling idle capacity at the org level can ensure stable BigQuery costs across the organization. Consideration also needs to given be to whether the location supports multi-region commitments or if separate commitments will need to be purchased for each region or location where workloads are provisioned.

CloudWatch

Monitoring – Waste

To reduce ingestion costs, stop ingestion of unnecessary logs. To reduce storage costs, change the retention period for your log groups. To reduce ingested log data scanned for CloudWatch Logs Insights queries, run queries for a shorter duration.

Database Optimization

BigQuery – Waste

Optimize the structure of queries and tables / databases to limit quantity of data scanned.

Dynamo DB Backups

Database – waste

Check how often you are running full DynamoDB backups; they could be running every 5 minutes with no retention policy. Over time these costs compound. Determine if the business requires this much backup data, if not one option is to switch to a solution of using point-in-time recovery for Dynamo.

EBS - Abandoned Volumes

Storage – Waste

Scripts can be implemented to scan and terminate unattached EBS volumes. Consider taking snapshots in higher environments before terminating the volumes. Many scripts can be found in github or elsewhere on the Internet.

EBS - Migrate to Newer Types

Storage – Efficiency

We saved 20% on some of our EBS costs by migrating from the gp2 to the gp3 EBS volume type.

GKE - Containers and Managing Capacity

Compute – Waste

Provision to balance capacity and requests to prevent inadvertent auto scaling. Leverage [GKE metering](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-usage-metering) and dashboards to understand the profile of workloads and address under- or over-provisioning.

Hybrid Use Benefits

Marketplace / Licensing – Waste

Manually look in Azure by selecting a virtual machine and then reviewing its properties. See if the AHUB Azure hybrid use benefit box is checked or not.

Idle VMs

Compute – Waste

Totally inactive compute; Azure Advisor can surface underutilised, look for those with shutdown recommendation and ask teams to validate.

Kubernetes Control Plane

Compute – Efficiency

Reduce number of clusters (only GKE and EKS). Abandoned clusters cost $.10 per hour.

Load Balancers (AWS)

Network – Waste

This type of waste can be identified through Trusted Advisor in the AWS console. However, Trusted Advisor is available only for Business and Enterprise Support customers. All AWS customers regardless of support level can use this CUR query from CUR query library to identify Idle load balancers.

Marketplace Licenses - Pay as you Go

Marketplace / Licensing – Waste / efficiency

Manually investigate the largest vendor spend. Create scripts that swaps out license sizing and the infrastructure underneath.

Network Interface Cards (NICs)

Network – Waste

Create a workflow to delete unused Network Interface Cards (NICs) from Azure VMs since NICs unattach, but do not delete when VMs are removed.

Object Storage Lifecycle

Storage – Waste

Manage object storage lifecycles to move data to nearlline or coldline when infequenlty accessed; remove obsolete versions / duplicates.

Optimizing AWS Athena Costs

Serverless – Waste

One common optimization technique is to partition tables using relevant attributes, such as date or location, to reduce the amount of data scanned. For example, if a table contains daily sales data, partitioning the table by date allows queries to scan only the relevant partitions for a specific date range, rather than scanning the entire table. This can result in major cost savings, as the amount of data scanned is greatly reduced.

Provisioning Object Storage in AWS

Storage – Waste

When using AWS S3 for storage, it’s crucial to consider object versioning and lifecycle management to avoid unnecessary costs. AWS S3 allows for the creation of multiple versions of the same object, and each version will incur additional storage charges. Therefore, it’s important to determine how to manage their lifecycle through different storage classes, including Standard, Intelligent-Tiering, Infrequent Access, and Glacier.

Snapshot Lifecycle

Storage – Waste

There are multiple ways to attack a lifecycle of snapshots in general. With EBS, you can use Amazon Data Lifecycle Manager to automate the retention of your snapshots. You can also use a myriad of 3rd party tools to help manage the data lifecycle of snapshots. I recommend first establishing a policy within your organization, communicate & collaborate on the policy, and enforce the policy with the ability to opt out.

Start/Stop VMs v2

Compute – Efficiency

Use the Azure Start/Stop VMs v2 to start and stop Azure Virtual Machines across multiple subscriptions. Users can define scheduling, generate insights, and get notifications to inform other efficiency tactics.

Unattached Disks

Storage – Waste

Azure portal -> Disks -> Filter where Owner = “-” to list all unattached across all subscriptions you have read access to.

Unattached Elastic IPs

Network – Waste

Unattached EIP cost $0.005 an hour. Over time this can compound into a waste of money. Also if there is something causing these EIPs to be unattached this problem will grow.

AWS Config

AWS Config provides oversight and information about all resources. With manual review we can understand all resources that are present in our environment and make sure we understand every resources that generate expense.

AWS Elastic Container Registry (ECR)

Stored GB and Transfer Out

While in the midst of production, software engineers frequently experiment with various application versions, leading to the generation of a substantial volume of images in a relatively brief period. This can result in a significant accumulation of redundant or unnecessary images, with some potentially featuring extensive debugging symbols that demand considerable storage capacity. To efficiently curtail wastage, organizations can swiftly optimize their resources by ensuring that images remain compact, either through the utilization of Alpine or dedicated images, and by promptly eliminating superfluous ones.

DynamoDB Optimization

Request Units

Optimizing Dynamodb Request units provides saving oportunity on an hourly basis, which will generate saving opportunity on the long run.

EC2 & RDS Scheduling

EC2 & RDS charged by hour

Scheduling EC2 and RDS instances allows instances to be “turned on” only when needed. This solution helps reduce operational costs by stopping resources that are not in use and starting them when they are needed. The Instance Scheduler automates the starting and stopping of Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Relational Database Service (Amazon RDS) instances through the use of Cloud Formation templates. Highest risk in production, while medium to low risk in development.

EC2 Autoscaling

Increase/Decrease Compute Capacity

Amazon EC2 Auto Scaling is designed to optimize costs by automatically adjusting the number of EC2 instances based on demand or workload. This approach can result in significant cost savings compared to a static setup where a fixed number of instances are always running, regardless of actual demand. Organizations often report savings of around 20-60% when moving from a static environment to an Auto Scaling setup, but the range can vary widely depending on the factors mentioned above. To get a precise calculation, a thorough analysis of specific workload patterns and Auto Scaling configurations is essential.

Managed Services

Per hour

View breakdown of your managed service instance types. Use this information to influence architecture teams to modernise these instances as the re-architecture lift tends to be lower than EC2 modernization efforts. Modernizing managed service architecture (RDS, OpenSearch, ElastiCache and Redshift) benefits as newer instances are cheaper and faster. Also, by consolidating machine types the risk associated with commitment management is reduced.

RDS Unused

Database instance hours

Evaluating DB connection count can help us identify unused DB instances. With the provided playbook we can dive deeper into finding rouge databases.

S3 Lifecycle Policy

Class type (accessibility, redundancy, region, data transfer), stored GB

To analyse current S3 bucket configuration vs. required usage, and optimize your configuration accordingly to reduce cost while maintaining application performance.

Single Use Blob Lifecycle Policy

Price per GB

For business use cases requiring to store Azure blob data at lower costs for longer duration which doesn’t need to be accessed, Blob Archive access Tier is the answer. Azure offers different access tiers (Hot/Cold/Archive) to store Azure blobs, with more cost efficiency, based on retention and access requirements. The appropriate access tier can be set for new blobs during initial upload or for existing blobs either manually or by using Azure Storage Lifecycle Management feature. To automate the process of updating access tier for blobs we can utilize Azure Storage Life Cycle Management policies where rules are set to move the blobs to different access tiers based on defined conditions. Note that the policies only run once a day with no user intervention.

Unused App Service Plans

Price per hour

Azure App Service Plan defines underlying compute resources for App services(web apps)/Azure Functions/Logic Apps to run. A single App Service Plan can host multiple apps. When all the underlying Azure apps in a plan are deleted but the plan is left intact by Azure engineers then it results in an unused App Service plan. An unused App service plan, with the exception of Dynamic or Free pricing tier plans, will continue to incur charges based on its configured pricing tier. As a good FinOps practice to reduce cloud wastage spend, it’s recommended to regularly review App service plans and any unused plans are promptly actioned upon to minimize the cloud charges. The unused app service plans can be deleted if not required anymore or scaled down to free tier as applicable.

Unused Azure Private Link Services

P / HR & Data processed

Unused Azure Private Links are private links that aren’t used in a running deployment. Although Microsoft doesn’t charge for the service it’s good practice to remove any Private Link Service that’s no longer being used and has no Private Endpoints attached to it. Azure Private Links enable you to access Azure PaaS Services (for example, Azure Storage and SQL Database) and Azure hosted customer-owned/partner services over a private endpoint in your virtual network. Please see the attached playbook for more details.

VM Rightsizing

p/ HR

VM’s can be sometimes chosen without proper alignment with the workload. This means it is over- or underutilized. This optimization tactic entails the rightsizing of the VM, i.e. to align with the workload properties.

Thank you to all our contributors

Rich Hoyer

Rich Hoyer

SADA
Steph Gooch

Steph Gooch

AWS
Eric Mulartrick

Eric Mulartrick

Boomi
Dennis Chang

Dennis Chang

Personal Project
Anthony Bothe

Anthony Bothe

Procter & Gamble
Scott Lapish

Scott Lapish

Telus
Joe Daly

Joe Daly

FinOps Foundation
Mike Martin

Mike Martin

GLG
Pete Silva

Pete Silva

Yahoo
Noel Crowley

Noel Crowley

Fidelity Investments
Bhups Hirani

Bhups Hirani

Kainos
Andy Foley

Andy Foley

Nationwide Building Society
Noah Abrahams

Noah Abrahams

Oracle

Make Suggestions

Suggest a Resource