Introducing AWS cost troubleshooting for DevOps teams

December 22, 2022
min. read
Edan Gilboa
Related Resource(s)
No items found.


The more you know, the more you save

We understand how difficult it can be to fully understand what total cloud costs are: direct and indirect costs, applied credits, auto-scaling. But you can't bury your head in the sand and ignore them - you have to look them straight in the eye!

Our engineering teams had the same frustrations trying to understand exactly what we are paying for when it comes to AWS bills. It's the same thing we encounter in life - unexpected dentist costs or a car breaking down. When you're running your infrastructure in the cloud, you want total control of your monthly spend.

Understand the cost structure to win

The first step to controlling and troubleshooting your AWS spend is to fully understand how it's structured. To give you this understanding, we use our deterministic mathematical model (the CloudTwin) to simulate cloud environments in real time. This means there are no unknowns - we give you a complete picture of your cloud at all times. Your cloud environment now has a digital twin that lets you comprehend the exact outcome of the cloud configuration changes you make, which now includes knowing exactly how much these changes cost.

Get answers to burning AWS cost questions

With this fresh approach to AWS costs, finally you can get answers to some of the most difficult cloud cost questions:

  • How much did auto-scaling groups cost us last month?
  • Are we optimizing data egress cost for data shared with partners? Ingress between regions?
  • How did we accumulate these network line items on our cloud bill? Which apps consumed that?

This is a big deal!

Existing solutions (native tools and legacy FinOps vendors) do a good job of reporting the upticks in your cloud cost. Yet they completely miss the context of resources in your environment and the network traffic of your cloud. When there's an uptick in cost, your DevOps and platform teams need to review the configuration changes and the actual traffic of your environment to fully understand total cloud cost. Only then, can you start optimizing and implementing best practices. Troubleshooting costs requires a complete and accurate picture of what you are paying for and the why.

4 use cases you can implement today

Here are 4 cool AWS cost use cases you can achieve with this approach today:

1. Look into the cost associated with cloud asset tags and review the trend of a specific tag, dive into the exact resource type/specific resources that caused the uptick in cost.

2. Review the cost trend and the configuration, complete with every change that took place and how these changes affected the cost postur

3. Use out-of-the-box cost optimization rules (architectural standards) or create your own cloud spend rules to implement cost best practices

4. Report on unused resources, high cost traffic or unexpected upticks in your environment in real-time.

Start troubleshooting AWS cost today

Effective cost troubleshooting requires understanding the full cloud picture, don't let your cloud bills hinder your cloud strategy.


Book a demo with our experts to see you can troubleshoot AWS cost today!

What's new

What's new