A policy instance allows an existing policy definition to take effect for all of the application provisioning activities in a specific deployment environment.

Verify that your user account has the ROLE_CLOUD_ADMIN cloud administrator role assigned to it.

Depending on your cloud provider, you must have at least one vCloud Director, vCloud Automation Center, or Amazon EC2 deployment environment mapped in vCloud Application Director. See Create a vCloud Director Deployment Environment, Create a vCloud Automation Center Deployment Environment, or Create an Amazon EC2 Deployment Environment.

If you are using a custom policy, verify that it is available in the catalog. See Add a Policy to the Catalog.


On the vCloud Application Director title bar, click the drop-down menu and select Clouds > Deployment Environments.


Select an existing deployment environment.


Select the Policy Instances tab and click Create Policy Instance to create a policy instance.


Complete the policy instance information for the deployment environment.



Name and Description

Include the policy name in either of these fields. The text from these fields appears in the policy instances section for the deployment environment.


If the policy does not appear in the drop-down list, cancel the dialog box and select Catalog > Policies to add a custom policy to the catalog.


Click the down arrow to select from a list of versions that are associated with the policy.


Select this check box to stop operations that can result in a non-compliant deployment, irrespective of current compliance state of deployment.

Before you use this option, it is recommended that the policy compliance is fully established in a deployment environment. A non-critical policy instance marks the compliance status of the deployment but does not stop the operation.


If you specify a new property value in the policy instance, the new property value overrides the existing catalog value defined in the policy.

The properties and scripts defined in the policy version are automatically populated in the Properties and Actions sections.

When you create a policy action script, the policy instance makes a copy. Changes to the policy script in the catalog do not affect the existing policy instances associated to that policy. You need to create a policy instance for the script changes to take effect.


Click Save when you finish.


Click the arrow next to the policy instance name to return to the previous page.