Category: Cloud Cost Optimization

Starting today, AWS Compute Optimizer will give recommendations to clean up idle resources. AWS Compute Optimizer historically has been focused on providing rightsizing recommendations to save cost and improve performance. To help you drive further cost savings, we are expanding the focus to now include detecting and recommending cleanup of idle recommendations. With this launch, you will get recommendations for idle EBS volumes, ECS tasks on running on Fargate, EC2 instances, EC2 Auto Scaling groups, and RDS instances.

We’re excited to announce the release of AWS Cloud Financial Management digital training courses. These are four 1-hour courses that will get you familiarized with key AWS solutions to solve your daily FinOps needs, and equip you with cost optimization techniques for commonly used AWS services.

We want to show you the benefits of CUR 2.0 and provide steps on how to migrate to CUR 2.0, so you don’t lose out! CUR 2.0 builds upon the Legacy CUR, while offering several key improvements for your cost tracking. Both 2.0 and Legacy allow you to analyze AWS costs in greater detail and accuracy, especially by including Resource IDs and hourly time granularity.

You can use Amazon Athena, a lightweight serverless, analytics tool, to query your AWS Cost and Usage Report (CUR). This enables you to dive into your cost and usage data for spend reporting and optimization analysis. However, you may not know all the opportunities you can optimize your Amazon S3 costs by taking advantage of S3 Lifecycle configuration.

As many organizations are looking to achieve financial success through effective Cloud Financial Management (CFM) strategies, Infor, the global leading software provider, has been experimenting with different practices, from cost reporting to optimization. In this blog post, we will share their success and learning that helped achieve over $2 million in savings through automation and modernization initiatives.

This blog shows how you can automatically propagate account-level tags to AWS resources created by AWS Service Catalog. Service Catalog allows sharing of portfolios across AWS accounts and provides a TagOption library to manage tags on provisioned AWS resources. Resource tagging varies by account, so it is not part of the portfolio product configurations. We designed the solution to reduce the burden on users to a minimum, while also adopting cloud best practices such as infrastructure automation.