Comment on page
Understanding Hava generated cloud diagram cost estimates.
When viewing hava interactive infrastructure diagrams you will see cost estimates have been calculated and are noted against the environment and detailed in the attributes of individual resources.
These are estimated costs and should only be used as a rough guide to anticipate what your monthly cloud spend is likely to be.
When you initially view your environment, you will see a Monthly Estimate breakdown displayed next to your diagrams.
The cost estimate is also displayed in the attribute pane when individual resources are selected on the diagrams
In this example an AWS EC2 Instance is selected
The cost estimates are also displayed alongside every resource in the Hava "List View"
To estimate the cost of each individual resource, we import the cost price data directly from AWS, Azure and Google Cloud. We then use the attributes of the resources detected in your imported infrastructure to estimate what it would cost to run for 24 hours a day for the entire month.
For example, to get the price for an AWS EC2 Instance, we use the instance type, region and platform to get the "per-hour" pricing which is then extrapolated to give the monthly estimate.
Hava currently only matches standard pricing data for the resources detected themselves. Because Hava only detects resources that are present and does not interrogate any data or traffic activity on your network, we cannot estimate or determine the value of data transfer, requests, discounts or other pricing factors that cloud providers will charge for but are not returned in the resource attributes.
We currently estimate costs based on "on-demand" pricing levels and do not take into consideration account reservations or spot pricing.
This means that while the cost estimate provided with your interactive infrastructure diagrams is a good indication of what your environment is likely to cost, the accuracy cannot in any way be considered absolute.