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

A quick primer on IAM

Until now, we’ve been acting as though creating anomaly detection monitors, running queries on the CUR, and even creating an entire organization is as simple as logging into the management account and doing as you please. Fortunately (or unfortunately?), it’s not as simple as we’d like it to be. In fact, even logging into the management account shouldn’t be as easy as logging into your preferred social media platform.

First, you have to prove who you are. We’re all familiar with the process of authentication by providing a username and password. There’s no shortage of web applications that follow this commonly accepted practice – it’s not much different on AWS. You can associate usernames and passwords to AWS accounts, allowing principals to authenticate their identity using what they know (i.e., a password). You can (and should) enforce an additional layer of authentication using what they have, namely...