A cloud administrator can review network resources that are exposed through data collection. The cloud administrator might choose to apply tags directly to the resources, to label capabilities for matching purposes in Cloud Assembly provisioning.

Networks, or subnets if you are working with Amazon Web Services or Microsoft Azure cloud accounts, are the IP-specific components of an available network domain.

The networks, or subnets, listed on the Cloud Assembly Networks page are defined externally in the network domain for your vendor account (Amazon Web Services or Microsoft Azure) or vCenter-based cloud accounts.

A network component in a blueprint can be defined, by using its networkType setting, as either existing, public, private, or outbound.

You can add or change aspects of these networks, such as adding new IP ranges or changing aspects of selected network's such as its CIDR, support for public IP access, and default gateway settings.

Networks that support public IP are not selected for blueprint deployments that require outbound-only or private network traffic.

Network tags are applied to every instance of that network, regardless of any network profiles in which the network may reside. Networks can be instanced into any number of network profiles. Regardless of network profile residency, a network tag is associated with that network wherever the network is used. Network tag matching occurs with other components in the blueprint after the blueprint has been matched with one or more network profiles.

For related information, see What are Network Profiles and Working with Networks and Network Profiles.