Leveraging Shared Services in AWS

AWS
by Girish Kurup

There were many Test accounts and Production account created in AWS by various teams categorized as 5 + Test accounts (~ 3k per month each ) and 5+ Prod accounts (~ 4K per month each). We rearchitecuted the AWS ecosystem by having a hub and spoke model. With shared services accounts as the hub for generic security, monitoring, risk, compliance, centralize DevOps and organization policies and spokes representing each tenant. For each tenant we organized PROD resources and TEST resources in separate VPCs under the same account. And set up shared generic services for each tenants. Savings of 15% plus at the same time centralized finance and automated DevOps operations for central IT operations team. Cost saving optimization along with adoption of cloud native Tools like DevOps. Happy tenants and happy finance stakeholders..

Related Member Stories

A Guide for Adopting FinOps in Your Organization

AWS
Azure
GCP
Industry: Internet
Persona: FinOps Practitioner
by F2 Working Group, FinOps Foundation

One of the biggest challenges in starting a FinOps practice is getting broad executive support and buy-in to dedicate the time and resources needed for the cultural change.

Read more

Removing AMI Snapshots

AWS
by Stephanie Gooch, AWS

Upon reviewing the amount of snapshots a customer had we found a large proportion of them were created from AMIs. This was found by listing all available amis in and connecting them back to the snapshot using the description. However, many of the AMIs that created them had been released....

Read more

Architecting Cloud Workloads for Financial Reporting

AWS
Azure
GCP
Industry: Information Technology & Services
Persona: FinOps Practitioner
by Rich Hoyer, SADA

A list of best practices for cloud architects to design systems to optimize FinOps.

Read more