New Feature: Savings Opportunity Usage Context

Cloudthread launched Savings Opportunity Usage Context so that engineering team members tasked with acting on a savings opportunity can get all the context they need to take action.

Each Savings Opportunity contains context on:

1. The resource cost history
2. A description of the savings opportunity and the thresholds used to evaluate the opportunity
3. The resource CloudWatch metric utilization history that was referenced to create the Savings Opportunity (e.g. for RDS Rightsizing: Database Connections, Max CPU Utilization, Max Memory Utilization)
4. Where the resource is in your environment (Account/Region)
5. The resource configurations (e.g. for RDS: MultiAZ, Engine, DBName, Iops)

Save time: Don’t go digging into Cloudwatch or your Observability platform to evaluate savings opportunities.

Coming soon: code snippets for copy/paste CLI resolution and GitHub PR generation for one-click resolution.

Frequently Asked Questions:

1. How much cost context is included?
   30 day context is included by default but with a single click you can see the resource cost context in the Cost Lab and see the resource context as far back as the Cost and Usage Report has existed (at least since your Cloudthread integration).
2. Is the same CloudWatch Usage Context provided for every resource?
   No, the CloudWatch data provided depends on the Savings Opportunity Category and the Savings Opportunity Service. You’ll see the metrics used to compute the Savings Opportunity and other generally relevant usage context for that service.