In the general case, Cloud scanner perform a separate inventory of instances and block storage.
When estimating impacts, CS adds the impacts of instance and block storage.
In Boavizta API The archetype of most aws instances are configured with a zero sized storage, so counting separately (and summing) the impacts of instances and storage is not an issue. Example: a1.4xlarge
See the definition of aws archetypes here: https://github.com/Boavizta/boaviztapi/blob/main/boaviztapi/data/archetypes/cloud/aws.csv
Howether, some instances are configured with non zero sotrage in Boavizta API. Example: c1.medium
We should investigate if this does not lead to double accounting of the storage.
In the general case, Cloud scanner perform a separate inventory of instances and block storage.
When estimating impacts, CS adds the impacts of instance and block storage.
In Boavizta API The archetype of most aws instances are configured with a zero sized storage, so counting separately (and summing) the impacts of instances and storage is not an issue. Example:
a1.4xlargeSee the definition of aws archetypes here: https://github.com/Boavizta/boaviztapi/blob/main/boaviztapi/data/archetypes/cloud/aws.csv
Howether, some instances are configured with non zero sotrage in Boavizta API. Example:
c1.mediumWe should investigate if this does not lead to double accounting of the storage.