Book Image

AWS FinOps Simplified

By : Peter Chung
Book Image

AWS FinOps Simplified

By: Peter Chung

Overview of this book

Much like how DevOps is a combination of cultural philosophies, practices, and tools that advocate a collaborative working relationship between development and IT operations, FinOps encourages the same collaboration between technology and finance team, making it key relationship to establish and maintain for any thriving business. This book will help you understand how organizations with a mature FinOps practice can decentralize cost ownership to developer teams and encourage cross-functional collaboration between business, finance, and technology, enabling speed, innovation, and business growth. You’ll focus on structuring your organization to form the right FinOps team, including a Cloud Center of Excellence, and learn how to implement practical cost savings measures with AWS tools to optimize costs in both the short as well as long term. By the end of this cloud FinOps book, you’ll be ready to implement a successful Cloud FinOps practice for your organization to get the best value from the AWS cloud for your workloads.
Table of Contents (18 chapters)
Free Chapter
2
Part 1: Managing Your AWS Inventory
7
Part 2: Optimizing Your AWS Resources
12
Part 3: Operationalizing FinOps

Scaling FinOps for your organization

In this section, we’ll move away from the technical aspects of cost optimization and consider some low-tech approaches that will help scale your teams and your FinOps efforts. You will learn about the EventStorming processes, how to facilitate an EventStorming workshop, and effectively share FinOps knowledge with other teams.

EventStorming, FinOps style

EventStorming is a low-tech activity typically associated with the domain-driven design of software architecture. This is a tactical tool that teams use to share business domain knowledge that helps to design the software components of a system.

During an EventStorming session, participants identify and map the business process to support a business function. They outline a series of domain events, represented by sticky notes over a certain period. As the participants work through the session, they model the stakeholders, commands, external systems, software dependencies, and more...