Policy Hierarchies

A user in Virtana Platform can create multiple policies, but only one policy can be applied to an entity at a time. From the Settings > Policies page, a hierarchy of policies can be established to determine the order in which policies are implemented. There is a limit of 25 policies per organization per report type.

For example, assume you create one policy with a scope of analysis that impacts all AWS data sources. You set the Tag filter to include the Dev environment and Test environment. You retain the default policy constraints for this policy. You then create a second policy with the same scope, but modify the constraints. You can set the policy with the modified constraints to be implemented first. However, if that policy cannot be implemented because some constraint does not apply, then the policy with default settings would be used.

The same Attributes and Tags used in global Report Filters can also be used to define policies.

From the Cost Saving Opportunities page, you can view the details for any policy associated with a compute instance in the Recommendation Details table. From the policy configuration form you can apply various report filters and then view the potential affects of additional changes on the Affected Entities tab. You can then delete or commit the changes. Saving edits to a policy results in a recalculation, which immediately commits the changes.


Editing and saving a policy forces a recalculation of the entities in your environment. This can take as much as 15 minutes.