Find out how to apply environment categorisations in CloudCreator with this 3 minute video.
CloudCreator supports an optional 'Environment' categorisation on all services.
The Environment categorisation allows you to tag each resource as either Production, Staging, Test or Development (you decide the actual values). CloudCreator can then help you answer questions such as:
- I want to ensure that all my production VMs are backed up. Are they all backed up?
- I don't want to back up my test and development VMs. Are any backed up now?
- How much am I paying for my production vs my non-production resources?
Several CloudCreator reports group and/or filter resources by Environment. For example, the Resource Category Explorer and Billing Dashboards.
Environment values are applied at the resource level. The way they are applied differs by service, as described in the table below. This resource category also leverages CloudCreator’s automatic Ancillary Services Mapping to minimise data entry and maximise the benefit of entering category values.
|NZ Hosted Services||
For New Zealand hosted services (excluding Azure Stack), each resource can be assigned an Environment value inside CloudCreator.
AWS provides a 'tag' feature that lets you store your own 'attribute' information against each resource. This is the best place to store Environment information.
Early each day CloudCreator loads resource tags with the key ‘Environment’.
Azure and Azure Stack provide a 'tag' feature that lets you store your own 'attribute' information against each resource. This is the best place to store Environment information.
Currently CloudCreator only loads tags from Azure (offshore). Next, CloudCreator will load tags from Azure Stack.
Early each day, CloudCreator loads resource tags with the key “Environment’.