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

Optimizing object storage

We’ve discussed in great detail the on-demand provisioning of compute resources in the previous chapter. With all that compute capacity, whether you’re using EC2 instances or Lambda functions, you need somewhere to store your data. Fortunately, storage is just as easily and readily available on AWS as compute.

Amazon Simple Storage Service (Amazon S3) is widely used as a storage medium on AWS. But reducing waste on storage costs with Amazon S3 is going to depend on the application, because an application used for backup and archive is going to have different needs from an e-commerce site or a streaming video service.

Reducing Amazon S3 costs boils down to three concerns:

  • Where you store the data in S3
  • How often you retrieve that data
  • Where you move that data to

These concerns will differ based on the workload. For example, a backup workload will be less likely to have requests and retrieval requests than a video...