Highlights

According to past experience, the major benefits cited by IT managers and company executives when deciding to transition to the cloud are cost savings and predictability. Organizations hunt for the most effective way to install, manage, and update their cloud services in anticipation of a big cost reduction because, on average, they know they can save 14% just by switching to cloud SaaS. Why then does this not occur? That is exactly what occurred to our client in this case study. The client’s leadership team was interested in learning how we may manage cloud spending more effectively.

The Need

A sizable finance organization that is our client has gradually moved its operations to the cloud. The makeover, however, didn’t follow any technique or adhere to adequate architectural preplanning. The client was consequently presented with a disproportionate cloud cost and no knowledge of resource consumption and expenditure.

Business and Approach

We are all aware that one of the most recent methods for cloud cost management is called CloudFinancial Operations (FinOps). Implemented several strategies to lower the cost of certain of the services in AWS Accounts through the use of some automation techniques as part of cost optimization. We employed a variety of optimization strategies, including auto tagging, tag correction, report generation based on tags, ec2 instances deleting superfluous resources, among others.

Details

Cost optimization is the primary goal. In order to save labour, we automated a lot of the manual tasks. Additionally, all resources that used the function of tagging had some required tags attached to them so that identifying the owner of each resource was simple. By doing this, we were also able to lower the cost of each resource.

Tag Compliance

1. Synchronize all application’s necessary Tags from Finops database to resources in AWS.
2. Replace all resources with a specific application name and cost code with a different application name and matching cost code.
3. Generate tag compliance report for an application.
4. Generate cloudhealth cost reports
5. Tally up and determine the costs of the assets that were not allocated to an application: As an Optimization Engineer or Developer, it is our responsibility to locate and reconcile any provided service resource assets that have not been tagged or allocated from the Cloud Health. There shouldn’t be any resources left untagged for the specified service after reconciliation is finished. Upload any that can’t be tagged to the box folder for more research.
6. Update the Map Migrated tag for all resources attached: -Update/Add Map Migrated Tags for all resources in the spreadsheet attachment using the specified key and value.

Power Scheduling

1. Power scheduling reports for all non -prd accounts.
2. Power scheduling needs to be implemented for all non-prod EC2 resources, according to a non-prd account. Information about power scheduling for a Non Prod account is included in the spreadsheet. To ensure that all non-production resources are included to power scheduling, group the resources by the name of the application and contact and collaborate with the application owners.

Results

1. Other urgent projects are being funded with the money saved.
2. Predictions and budgets that are more accurate and efficient.
3. Dashboards, reports, and periodic cadence will increase transparency and visibility into summary costs and information for all assets, environments, and accounts.
4. Gains in overall operational efficiency brought about by improved team responsibility and continual attention to anticipating infrastructure needs