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

Grouping tags with AWS Cost Categories

At this point, you are aware of the AWS tools that can help provide an inventory of resources across your accounts. You know that you can apply tags and associate resources with meaningful organizational assets such as owners, applications, cost centers, and BUs. Combining these strategies and tools can help you start to identify resources that you can terminate.

AWS Cost Categories provides an additional layer of resource management and cost visibility. There may be cases where your tagging strategy is either too granular or too coarse to provide the information you need. For example, perhaps you organize your accounts to support multiple applications. You have a structure that mimics the one shown here:

Figure 3.8 – Using AWS Cost Categories to group tags together

Applications A, B, and C are their own OU. Within each OU, there are three accounts to represent different environments. You initially assign tags...