FinOps is the practice of cloud financial management. It requires cross-functional teamwork to identify the optimal trade-off between cost, speed, and agility, which is a balance guided by the strategic and tactical needs of the business.
During the first phase of public cloud adoption, most business units made their own buying and engineering decisions independently, as they often do during the early adoption phases of any new technology.
However, as cloud resource costs quickly became a significant portion of IT spending, the procurement process began to draw the attention of corporate executives who requested more transparency in the form of streamlined operations and standardized financial reporting. They understood the strategic value of controlling their expenses intelligently without hamstringing the company's ability to scale.
We are now in a phase of public cloud adoption where cloud purchasing is being centralized. This effort is typically led by a specialist in finance who negotiates pricing on the company’s behalf with the leading cloud providers and leads the implementation of a corporate cloud governance process.
With the maturation of cloud adoption, cross-departmental teams have been formed typically incorporating four groups of stakeholders: corporate executives, finance and procurement specialists, engineering and operations managers, and application or product owners. These teams are often led by a cloud procurement specialist. Their primary objective is to promote a culture of responsible spending without hampering innovation or business velocity.
Densify is a proud member of the FinOps foundation which is in turn under the purview of the Linux Foundation. The FinOps foundation leads the industry in advancing this discipline across industries, and as such has defined the core principles of financial cloud management which include a reference framework of best practices, and more importantly a paid training and certification program for practitioners.
Our goal for creating this FinOps collection of articles is to freely provide practitioners with best practices collected from dozens of engagements, as well as technical information, as the first step on their path to seeking formal training and certification from the FinOps foundation.
At a high level, our Guide to FinOps simply describes a set of activities required to establish a sense of collective responsibility towards spending on public cloud resources. Of course, you can’t manage what you can’t measure, and you can’t do it alone, so the emphasis of our approach is on measurement, analysis, collaboration, and enforcement. Each stage of our methodology is covered in a dedicated chapter of our FinOps guide.
Our pillars also align with the FinOps Foundation’s “FinOps Journey” phases:
The tools and APIs available from cloud providers are conceptually similar yet unique to each cloud provider. In our guide, we begin with covering technologies and tools specific to Amazon Web Services (AWS), and we will next publish information about Microsoft Azure and Google Cloud. Our product provides support for all cloud platforms, yet we will publish this guide in the order that we are writing the content.
We have organized our methodology into a matrix. The columns in the table below represent advancing stages of a governance process. The first table row introduces all of the basic concepts that a reader must become familiar with before being exposed to the best practices shared in the second row. The third row offers a drilldown into specific topics that deserve deeper learning. Our goal is to share the knowledge necessary for a FinOps practitioner to converse with the company’s engineering team, meet with the application owners, negotiate with cloud providers, and lead the implementation of a cross-departmental governance process.
|Primer||Learn about the challenges and native tools for organizing||Discover the challenges and tools to isolate cloud waste||Learn about challenges and native tools for purchase planning||Learn to collaborate using budgets and chargeback to enforce efficiency|
|Best Practices||Get recommendations for organizing your cloud resources||Learn best practices for achieving resource optimization and efficiency||Learn best practices for safely optimizing purchasing discounts||Learn collaboration best practices for reporting and early detection of anomalies|
|Drilldown||Delve into AWS Organizations and Tagging||Dig deeper into optimization concepts||Drill into AWS Savings Plans and Spot Instances||Explore AWS Budgets and Cost Allocation Reports|
The chapters outlined below align with the stages of our methodology as depicted in the table shown above. We are adding new articles every month to complete our chapters, so remember to bookmark this page to read our latest.
Become familiar with the concepts and tools designed to help you organize your spending such as AWS Organizations, Cost Explorer, Cost, Usage Reports, and Cost Allocation Tags.Read Chapter 1
Discover the intricacies of measuring computing resources and matching them to workload requirements, and learn the best practices of resource optimization.Read Chapter 2
Learn how to increase your purchase discounts by exploring various programs offered by AWS, and avoid misplaced commitments that can prove restrictive and costly.Read Chapter 3
Get help understanding the best practices for implementing a chargeback cost allocation model, and automate the reconciliation process between your expected and actual spending.
Use the field below to ask a question about FinOps or simply share feedback to help us improve. We select our topics based on popular questions.