A cloud administrator can review and edit network resources that are made available through endpoint data collection.
After you add a cloud account, data collection discovers the cloud account's network information and makes that information available for use. 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.
You can view existing networks and add or change aspects of these networks, such as adding new IP ranges or tags or changing aspects of a selected network 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.
You can use tags to match appropriate networks, and optionally network profiles, to network components in blueprints.
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.