| Info |
|---|
CloudAware Application is a logical unit that allows to organize resources according to a naming convention or a tag, or any other custom logic customers wish to apply. |
CloudAware Cloudaware Applications may be created to distinguishdifferentiate:
Department, Team, Site, Project within your organization
Customers, if you are an MSP
Purchasers, if you are a reseller, etc
...
Note that the sooner you create the application, the better since billing and cost data is not retrospective - it may be collected and shown in a Cloudaware application only starting the day when the application was created.
| Table of Contents |
|---|
Key Features
Multi-cloud and non-cloud support
Cascades provide the ability to attach object hierarchies by attaching a single object
Inventory automation using auto-attachment rules
The ability to attach objects that are not taggable or exceed the tag limit
Prerequisites
Think of resources that should be attached to the Cloudaware application. Consider the logic that can be used for attaching assets in question to different tiers of the application.
...
Cloudaware applications support cascades, meaning that all related objects will be cascadingly attached once a resource is attached to the application. For example, once you attach an AWS EC2 Instance, all corresponding EBS Volumes or Network Interfaces will also be attached.
Considerations:
When selecting an object to attach to a Cloudaware application, check if another object is above it in the hierarchy that can be connected first. For example, it's better to attach AWS ELB Load Balancer than related instances, it's better to attach AWS Elastic Beanstalk Application than AWS Elastic Beanstalk Environment, and it's always better to attach URLs.
Try to minimize manual attachments. For example, there is a logic for selecting objects that need to be attached to a specific application. Implementing that logic in an auto-attachment process is much better because Cloudaware will keep track of new assets that comply with the defined logic. If you still need to add some objects manually, attach only truly static resources.
Note that the cascades are sound but only work for extensive services with many interconnected objects. What should one do with all objects that have no relationships with each other? The answer is to implement the process that will monitor assets, automatically validate them against defined rules, and choose the application accordingly. These are application auto-attachment rules. Learn more