In Cloud Assembly, capability tags enable you to define placement logic for deployment of infrastructure components. They are a more powerful and succinct option to hard coding such placements.
You can create capability tags on compute resources, cloud zones, images and image maps, and networks and network profiles. The pages for creating these resources contain options for creating capability tags. Alternatively, you can use the Manage Tags page in Cloud Assembly to create capability tags. Capability tags on cloud zones and network profiles affect all resources within those zones or profiles. Capability tags on storage or network components affect only the components on which they are applied.
Typically, capability tags might define things like location for a compute resource, adapter type for a network, or tier level for a storage resource. They can also define environment location or type and any other business considerations. As with your overall tagging strategy, you should organize your capability tags in a logical manner.
Cloud Assembly matches capability tags with constraints from cloud zones and on blueprints at deployment time. So, when creating and using capability tags, you must understand and plan to create appropriate blueprint constraints so that matching will occur as expected.
For example, in the Add Cloud Zones topic in the Wordpress example, you created dev and test tags for the OurCo-AWS-US-East and OurCo AWS-US-West zones. This indicates that the OurCo-AWS-US-East zone is a development environment, and the OurCo-AWS-US_West zone is a test environment. Paired with the appropriate constraint tags, these capability tags enable you to direct deployments to the desired environments.