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

Understanding data transfer scenarios

Why do data transfer costs exist? Data transfer costs exist because various network boundaries exist within the AWS ecosystem and there is a cost associated with crossing those network boundaries. You might cross boundaries to get from the AWS network out to the internet, or cross boundaries to get from one AWS Region to another.

Within each AWS Region, there are at least two AZs. Each of these AZs can represent multiple data centers, and each AZ has its own infrastructure, such as power, cooling, and security. They’re connected with redundant ultra-low latency connections and are physically separate from each other. These clusters of AZs constitute a Region and are set apart to protect them from issues such as power outages and natural disasters, but are still close enough to support synchronous replication scenarios for your workloads.

Now, to take advantage of AWS’ global network, you can create a virtual network that spans...