Avoid and Simplify Shared Costs

AWS
by Joseph Daly, Nationwide

Nationwide’s strategy to handle shared costs is to avoid them as much as possible. We do this through our account and tagging strategies. We segment or accounts by department and sometimes by application so that if there are any untaggable expenses are at least identifiable to the account owner. We work with finance to make sure that each account has a default cost center so that 100% of all costs are allocable to the owner.

For shared platforms,like containers, we primary leverage a label strategy for cost allocation. We allocate cluster costs in proportion of each cost center label’s usage. Sometimes, depending on the application, we will dedicate clusters similarly as we do accounts. That way one department or application is being charged for the costs incurred as opposed to being spread out amongst the rest.

Due to company accounting policy and a desire to make our direct chargeback as transparent as possible, we do not allocate 100% of our bill directly through chargeback. Chargeback covers the vast majority of our expenses. For the remainder, items like enterprise support and accounts setup for management of the cloud, we set a budget and provide showback reporting to make these charges visible. They are not charged back directly, but we know who/what/where the costs are being driven from. Providing this keeps us aligned with enterprise accounting policies and keeps our chargeback simple and transparent.


Related Member Stories

A Guide for Adopting FinOps in Your Organization

AWS
Azure
GCP
Industry: Internet
Persona: FinOps Practitioner
by F2 Working Group, FinOps Foundation

One of the biggest challenges in starting a FinOps practice is getting broad executive support and buy-in to dedicate the time and resources needed for the cultural change.

Read more

Removing AMI Snapshots

AWS
by Stephanie Gooch, AWS

Upon reviewing the amount of snapshots a customer had we found a large proportion of them were created from AMIs. This was found by listing all available amis in and connecting them back to the snapshot using the description. However, many of the AMIs that created them had been released....

Read more

Architecting Cloud Workloads for Financial Reporting

AWS
Azure
GCP
Industry: Information Technology & Services
Persona: FinOps Practitioner
by Rich Hoyer, SADA

A list of best practices for cloud architects to design systems to optimize FinOps.

Read more