Configuration: IP Tag Collection
Focus
Focus
Strata Cloud Manager

Configuration: IP Tag Collection

Table of Contents

Configuration: IP Tag Collection

Automate cloud IP-Tag collection and distribution in Strata™ Cloud Manager to enable dynamic security policies for your cloud workloads.
Where Can I Use This?What Do I Need?
  • NGFW (Managed by Strata Cloud Manager)
  • Cloud NGFW
  • Prisma Access
  • Strata Cloud Manager Essentials with Strata Logging Service
  • Any firewall or Prisma Access. VM-Series Firewall or AI Runtime Security firewall must be funded with Software NGFW Credits.
  • Network Administrator or Superuser role on the Customer Support Portal
IP-Tag Harvesting in Strata Cloud Manager (SCM) enables your firewalls to dynamically receive IP-to-Tag mapping information from various security providers, such as cloud providers and Zero Networks. This feature enables you to create Dynamic Address Groups (DAGs) from workload tags and use them in your security policies. This allows you to create security policies based on logical tags rather than static IP addresses, ensuring your policies automatically adapt as cloud workloads scale. This approach eliminates the manual effort of updating security rules for constantly changing cloud environments.
SCM acts as the central management platform for configuring and orchestrating IP-Tag Harvesting. You onboard your cloud accounts, such as AWS, Azure, or GCP, to SCM. This onboarding process, either manual with credentials or automated via Terraform, establishes the necessary permissions for SCM to access cloud provider APIs and harvest IP-Tag data. You then define Distribution Profiles in SCM, specifying firewall dynamic address group membership and roles (contributor or receiver). Additionally, you can harvest IP tags from Zero Networks; this allows you to collect tags for integrated policy.
You have two options to configure IP-Tag Collection—Terraform templates (recommended) or by manually entering the required information. Zero Networks integration does not support Terraform template configurations.

Configure IP Tag Collection with Terraform

Automate cloud IP-Tag collection and distribution in Strata™ Cloud Manager to enable dynamic security policies using Terraform templates.
This procedure guides you through connecting Strata Cloud Manager to your cloud environment for IP-Tag collection using Terraform templates.
  1. Log in to Strata Cloud Manager.
  2. Select ConfigurationCloud Identity EngineUser ContextIP-Tag Collection.
  3. On the IP-Tag Collection (Recommended) page, select Add New Cloud Account.
    If you are migrating from IP-Tag Collection Legacy, onboard a cloud account and complete this procedure under IP-Tag Collection (Recommended). After you save and see a successful connection, confirm that the tags you see match the expected values. Then delete the existing configuration under IP-Tag Collection Legacy so that tag collection and enforcement continue without interruption on the new infrastructure.
  4. Select your cloud service provider (AWS, Azure or Google Cloud Platform) and click Next: Configure Connection.
  5. To use Terraform (recommended), click Connect via Terraform (Recommended).
  6. Enter a descriptive Name.
  7. Enter the information, depending on your selected cloud service provider
    • AWS—Enter your AWS Account ID and the Role Name associated with your AWS account.
    • Azure—Enter your Azure Tenant ID and Subscription ID.
    • Google Cloud Platform—Enter your GCP Project ID and Service Account Name.
  8. Click Next: Integrate Cloud Account to continue.
  9. Download your Terraform template.
    • If you are familiar with Terraform click the Download Terraform.
    • If you are new to Terraform, follow the Guided Steps.
  10. Deploy the Terraform template in your environment. For AWS, enter the Role ARN from the Terraform output.
  11. Click Save Configuration.
  12. Verify the cloud service provider account connection status. A successful connection ensures that Strata Cloud Manager can communicate with your cloud environment and begin the tag discovery process.
    It may take a few minutes to establish a successful connection.

Configure Tag Distribution

  1. Create a new Tag Distribution for your onboarded cloud account.
    1. On the IP-Tag Collection page, choose a successfully connected cloud account.
    2. Click + Distribute.
  2. Define the scope for tag collection.
    1. Enter a descriptive Name.
    2. Enter a Polling Interval in seconds.
    3. Select Regions and VPC (AWS only).
    4. Optional For Azure deployments, select Fetch Service Tags. For more information about Azure service tag and Palo Alto Networks firewalls, see Attributes Monitored on Azure
  3. Select Tag Destination folders containing the firewalls intended to receive the IP-to-tag mappings. Specify the target for tag distribution.
  4. Save the Tag Distribution configuration. Saving the distribution settings makes them active within Strata Cloud Manager, preparing them for deployment to your firewalls.
  5. Push the configuration to your firewall.
    1. Navigate to ConfigurationPush Config.
    2. Select the relevant Admin Scope and Folder.
    3. Select Push. This synchronizes the cloud integration and harvested IP-to-tag mappings from Strata Cloud Manager to your managed firewalls, enabling granular Layer 7 security policies based on real-time asset classifications.
  6. Verify the connection status of the tag distribution.

AWS

Automate cloud IP-Tag collection and distribution in Strata™ Cloud Manager to enable dynamic security policies for your AWS workloads.
This procedure guides you through connecting Strata Cloud Manager to your cloud environment for IP-Tag collection and configuring Tag Distribution.
  1. Log in to Strata Cloud Manager.
  2. Select ConfigurationCloud Identity EngineUser ContextIP-Tag Collection.
  3. Onboard a cloud service provider account using manual credentials. This connects SCM to your public cloud environment, allowing SCM to discover and collect IP-Tag mappings.
    1. On the IP-Tag Collection (Recommended) page, select Add New Cloud Account.
      If you are migrating from IP-Tag Collection Legacy, onboard a cloud account and complete this procedure under IP-Tag Collection (Recommended). After you save and see a successful connection, confirm that the tags you see match the expected values. Then delete the existing configuration under IP-Tag Collection Legacy so that tag collection and enforcement continue without interruption on the new infrastructure.
    2. Select your cloud service provider and click Next: Configure Connection.
    3. Select the Connection Type as Terraform (Recommended) or Enter Credentials Manually.
    4. Enter a descriptive Name.
    5. Enter your AWS Access Key ID, Secret Access Key, and confirm the Secret Access Key.
    6. Optional Enter Role ARN Name and Role ARN Value. Click Open CFT to open the cloud formation templates for more information about configuring Role ARN. See IAM Roles and Permissions for Panorama in the VM-Series Deployment Guide for an example and more information.
    7. Optional Select a region from the Regions drop-down menu.
    8. Optional Test Connection between Strata Cloud Manager and your AWS environment.
  4. Click Save Configuration.
  5. Verify the cloud service provider account connection status. A successful connection ensures that Strata Cloud Manager can communicate with your cloud environment and begin the tag discovery process.
    It may take a few minutes to establish a successful connection.

Configure Tag Distribution

  1. Create a new Tag Distribution for your onboarded AWS account.
    1. On the IP-Tag Collection page, choose a successfully connected cloud account.
    2. Click + Distribute.
  2. Define the scope for tag collection.
    1. Enter a descriptive Name.
    2. Enter a Polling Interval in seconds.
    3. Select Regions and VPC.
  3. Select Tag Destination folders containing the firewalls intended to receive the IP-to-tag mappings. Specify the target for tag distribution.
  4. Save the Tag Distribution configuration. Saving the distribution settings makes them active within Strata Cloud Manager, preparing them for deployment to your firewalls.
  5. Push the configuration to your firewall.
    1. Navigate to ConfigurationPush Config.
    2. Select the relevant Admin Scope and Folder.
    3. Select Push. This synchronizes the AWS integration and harvested IP-to-tag mappings from Strata Cloud Manager to your managed firewalls, enabling granular Layer 7 security policies based on real-time asset classifications.
  6. Verify the connection status of the tag distribution.

Azure

Automate cloud IP-Tag collection and distribution in Strata™ Cloud Manager to enable dynamic security policies for your Azure workloads.
This procedure guides you through connecting Strata Cloud Manager to your cloud environment for IP-Tag collection and configuring Tag Distribution.
  1. Log in to Strata Cloud Manager.
  2. Select ConfigurationCloud Identity EngineUser ContextIP-Tag Collection.
  3. Onboard a cloud service provider account using manual credentials. This connects Strata Cloud Manager to your public cloud environment, allowing Strata Cloud Manager to discover and collect IP-Tag mappings.
    1. On the IP-Tag Collection (Recommended) page, select Add New Cloud Account.
      If you are migrating from IP-Tag Collection Legacy, onboard a cloud account and complete this procedure under IP-Tag Collection (Recommended). After you save and see a successful connection, confirm that the tags you see match the expected values. Then delete the existing configuration under IP-Tag Collection Legacy so that tag collection and enforcement continue without interruption on the new infrastructure.
    2. Select your cloud service provider and click Next: Configure Connection.
    3. Select the Connection Type as Terraform (Recommended) or Connect via Enter Credentials Manually.
    4. Enter a descriptive Name.
    5. Enter your Azure Client ID and Client Secret.
    6. Enter your Azure Tenant ID and Subscription ID.
    7. Optional Test Connection between SCM and your Azure environment.
  4. Click Save Configuration.
  5. Verify the cloud service provider account connection status. A successful connection ensures that SCM can communicate with your cloud environment and begin the tag discovery process.
    It may take a few minutes to establish a successful connection.

Configure Tag Distribution

  1. Create a new Tag Distribution for your onboarded Azure account.
    1. On the IP-Tag Collection page, choose a successfully connected cloud account.
    2. Click + Distribute.
  2. Define the scope for tag collection.
    1. Enter a Tag Distribution Name.
    2. Select Cloud Service via API as the Tag Collection Type.
    3. Select Resources as VM Workload.
    4. Enter a Polling Interval in seconds.
    5. Click Next: Select Tag Source.
  3. Define the tag source.
    1. Select Regions.
    2. Enable Fetch Service Tags. For more information about Azure service tag and Palo Alto Networks firewalls, see Attributes Monitored on Azure.
  4. Click Select Tag Destination folders containing the firewalls intended to receive the IP-to-tag mappings. Specify the target for tag distribution.
  5. Save the Tag Distribution configuration. Saving the distribution settings makes them active within Strata Cloud Manager, preparing them for deployment to your firewalls.
  6. Push the configuration to your firewall.
    1. Navigate to ConfigurationPush Config.
    2. Select the relevant Admin Scope and Folder.
    3. Select Push. This synchronizes the Azure integration and harvested IP-to-tag mappings from Strata Cloud Manager to your managed firewalls, enabling granular Layer 7 security policies based on real-time asset classifications.
  7. Verify the connection status of the tag distribution.
  8. When the connection is established, go to IP-Tag CollectionIP-Tag Collection (Recommended)IP-Tag Collection for Cloud Services TAG DISTRIBUTION and select the number associated with your Cloud account.
    You can see the Tag Distributions status here.
  9. Select your account to check the Tag Mapping Data.

GCP

Automate cloud IP-Tag collection and distribution in Strata™ Cloud Manager to enable dynamic security policies for your GCP workloads.
This procedure guides you through connecting SCM to your cloud environment for IP-Tag collection.
  1. Log in to Strata Cloud Manager.
  2. Select ConfigurationCloud Identity EngineUser ContextIP-Tag Collection.
  3. Onboard a cloud service provider account using manual credentials. This connects Strata Cloud Manager to your public cloud environment, allowing Strata Cloud Manager to discover and collect IP-Tag mappings.
    1. On the IP-Tag Collection (Recommended) page, select Add New Cloud Account.
      If you are migrating from IP-Tag Collection Legacy, onboard a cloud account and complete this procedure under IP-Tag Collection (Recommended). After you save and see a successful connection, confirm that the tags you see match the expected values. Then delete the existing configuration under IP-Tag Collection Legacy so that tag collection and enforcement continue without interruption on the new infrastructure.
    2. Select your cloud service provider and click Next: Configure Connection.
    3. Select the Connection Type as Terraform (Recommended) or Connect via Enter Credentials Manually.
    4. Enter a descriptive Name.
    5. Upload your GCP service account JSON file.
    6. Optional Test Connection between SCM and your GCP environment.
  4. Click Save Configuration.
  5. Verify the cloud service provider account connection status. A successful connection ensures that SCM can communicate with your cloud environment and begin the tag discovery process.
    It may take a few minutes to establish a successful connection.

Configure Tag Distribution

  1. Create a new Tag Distribution for your onboarded GCP account.
    1. On the IP-Tag Collection page, choose a successfully connected cloud account.
    2. Click + Distribute.
  2. Define the scope for tag collection.
    1. Enter a descriptive Name.
    2. Enter a Polling Interval in seconds.
    3. Select Regions.
  3. Select Tag Destination folders containing the firewalls intended to receive the IP-to-tag mappings. Specify the target for tag distribution.
  4. Save the Tag Distribution configuration. Saving the distribution settings makes them active within Strata Cloud Manager, preparing them for deployment to your firewalls.
  5. Push the configuration to your firewall.
    1. Navigate to ConfigurationPush Config.
    2. Select the relevant Admin Scope and Folder.
    3. Select Push. This synchronizes the GCP integration and harvested IP-to-tag mappings from Strata Cloud Manager to your managed firewalls, enabling granular Layer 7 security policies based on real-time asset classifications.
  6. Verify the connection status of the tag distribution.

Zero Networks

Automate cloud IP-Tag collection and distribution in Strata™ Cloud Manager to enable dynamic security policies using data from Zero Networks.
The Zero Networks integration with Strata Cloud Manager enables Strata Cloud Manager to acquire IP-to-tag mappings from the Zero Networks platform. This enhances network asset visibility and facilitates dynamic policy enforcement on your managed firewalls. This integration provides a unified solution for visualizing, segmenting, and securing lateral movement across your enterprise by combining Strata Cloud Manager's management capabilities with Zero Networks' agentless microsegmentation.
Strata Cloud Manager establishes a secure connection to the Zero Networks platform and periodically polls the Zero Networks platform to retrieve dynamically generated IP-to-tag mappings. These tags are based on attributes such as name, OS type, FQDN, and domain, from various Zero Networks groups including Active Directory (AD), Custom, System, Tags, OT/IoT, and ServiceNow.
The Strata Cloud Manager Cloud IP Tag Service processes and stores this harvested IP-to-tag information. Strata Cloud Manager then pushes these real-time IP-to-tag mappings to your managed firewalls as Dynamic Address Groups. Your firewalls leverage these Dynamic Address Groups to apply granular Layer 7 security policies, such as Advanced Threat Prevention and Advanced URL Filtering, based on the specific classification of network assets. These dynamic updates ensure your security policies remain current as assets are discovered or change behavior.
The Cloud IP-Tag Collector supports up to 15,000 members per profile for each Zero Networks account onboarded.
This procedure guides you through connecting Strata Cloud Manager to your Zero Networks deployment.
  1. Log in to Strata Cloud Manager.
  2. Select ConfigurationCloud Identity EngineUser ContextIP-Tag Collection.
  3. Onboard a Zero Networks account using manual credentials. This connects SCM to your Zero Networks deployment, allowing SCM to discover and collect IP-Tag mappings.
    1. On the IP-Tag Collection (Recommended) page, select Add New Cloud Account.
    2. Select Zero Networks and click Next: Configure Connection.
    3. Enter a descriptive Name for the connection configuration.
    4. Add your Zero Networks Token obtained from your Zero Networks portal.
      If your Zero Networks token expires, Strata Cloud Manager pulls no tags until the expired token is renewed.
    5. Optional Click Test Connection to verify that your token is valid.
  4. Click Save Configuration.
  5. Verify the cloud service provider account connection status. A successful connection ensures that Strata Cloud Manager can communicate with your cloud environment and begin the tag discovery process.
    It may take a few minutes to establish a successful connection.

Configure Tag Distribution

  1. Create a new Tag Distribution for your onboarded Zero Networks account.
    1. On the IP-Tag Collection page, choose a successfully connected cloud account.
    2. Click + Distribute.
  2. Define the scope for tag collection. Specifying regions and groups ensures that only relevant IP-to-tag mappings are collected, optimizing performance and data relevance for your security policies.
    1. Enter a descriptive Name.
    2. Enter a Polling Interval in seconds, between one and 30 minutes.
  3. Select Tag Destination folders containing the firewalls intended to receive the IP-to-tag mappings. Specify the target for tag distribution.
  4. Save the Tag Distribution configuration. Saving the distribution settings makes them active within Strata Cloud Manager, preparing them for deployment to your firewalls.
  5. Push the configuration to your firewall.
    1. Navigate to ConfigurationPush Config.
    2. Select the relevant Admin Scope and Folder.
    3. Select Push. This synchronizes the Zero Networks integration and harvested IP-to-tag mappings from Strata Cloud Manager to your managed firewalls, enabling granular Layer 7 security policies based on real-time asset classifications.
  6. Verify the connection status of the tag distribution.

Manage and Migrate Existing IP Tag Collection Configurations

Collect cloud IP-Tags in Strata Cloud Manager using a credential configuration and a monitor configuration.
If you are migrating from IP-Tag Collection Legacy, onboard a cloud account and complete this procedure under IP-Tag Collection (Recommended). After you save and see a successful connection, confirm that the tags you see match the expected values. Then delete the existing configuration under IP-Tag Collection Legacy so that tag collection and enforcement continue without interruption on the new infrastructure. However, if you want to manage your existing configuration, use this procedure.
The Legacy configuration flow collects IP address-to-tag information from your cloud service provider using two linked objects: a credential configuration, which stores the credentials Strata Cloud Manager uses to reach the provider, and a monitor configuration, which defines what to collect and where to send it. The Recommended flow replaces both with a single cloud account onboarding step.
Use the Legacy flow when you need a capability the Recommended flow does not provide, such as routing collection through a context collector in an air-gapped or restricted environment, or reusing one set of credentials across several monitor configurations.
To collect IP-tag information from your cloud service provider, you must first grant the Cloud Identity Engine the required permissions:
  • Amazon Web Services (AWS)—Grant the service account the Amazon Role Name (ARN) roles described in the IAM Roles and Permissions for Panorama section of the VM-Series documentation. For more information about the ARN, refer to the AWS documentation.
  • Microsoft Azure—Grant the read permissions described in the Azure Monitoring section of the VM-Series documentation to the service account.
  • Google Cloud Platform (GCP)—Grant the IAM roles described in the VM-Series documentation to the service account.
For each region, you can synchronize up to 60,000 IP-tag mappings from a cloud service in a monitoring configuration at one time. Only new or modified mappings are synchronized on each pass. You can view up to 32,000 IP-tag mappings per page.
  1. If you have not already done so, activate User Context and either use the default segment or configure a new segment to receive the mapping information.
  2. Select ConfigurationCloud Identity EngineUser ContextIP-Tag Collection, then select the Legacy tab.
  3. Select the Credential Configuration tab, if it does not already display.
  4. To Set Up a New Credential Configuration, select the cloud service provider you want to use.
  5. Enter a unique and descriptive Name for the configuration.
  6. (AWS only) Configure your AWS connection.
    To open your AWS administrator portal in a new window so that you can create or edit any necessary ARNs, select the type of CloudFormation template (CFT) you want to configure and log in with your AWS credentials.
    • Open CFT (Application Account Prerequisites) —Configure the application account prerequisites.
    • Open CFT (Security Account Prerequisites) —Configure the security account prerequisites.
    To enable monitoring using the current account, you only need to configure the application account prerequisites. To use a different account, such as a service account or a cross-account role, configure the application account prerequisites, the security account prerequisites, and a role ARN for the account.
    1. Enter your Access Key ID.
      To learn how to obtain your access key ID and secret access key, refer to the AWS documentation.
    2. Enter your Secret Access Key.
    3. Reenter your secret access key to Confirm Secret Access Key.
    4. Optional Enter a Role ARN Name and Role ARN Value.
      To configure additional Role ARNs, click Add Role ARN for each Role ARN you want to include.
  7. (Azure only) Configure your Azure connection.
    1. Enter your Client ID.
      To learn how to obtain the client ID and client secret, refer to the Azure documentation.
    2. Enter your Client Secret.
    3. Enter your Tenant ID.
      To learn how to obtain the tenant ID and subscription ID, refer to the Azure documentation.
    4. Enter your Subscription ID.
  8. (Google Cloud Platform only) Configure your GCP connection.
    1. Create credentials for a service account in your Google Cloud console, and then download and save the JSON file in a safe location.
    2. Click Browse files and click Open to navigate to the JSON file, or drag and drop the GCP credential JSON file.
    3. Optional Select the Region for the instance.
      You can optionally Search for a region. If you do not select a region, the Cloud Identity Engine uses the us-west-2 region. You can select one region per instance.
  9. Verify the connection by clicking Test Connection.
    (AWS and Google Cloud Platform only) You can optionally select the Region before you test the connection. By default, the Cloud Identity Engine selects the US West region; if this region does not enable API requests, select a region that does.
    Even if the connection test is not successful, you can still submit your configuration. Until you resolve the connectivity issues, the configuration status is Not connected. You must resolve the connection issues before the configuration can retrieve IP address-to-tag mappings.
  10. Submit the configuration.
    To collect and view your IP-tag mappings, you must also configure a monitor configuration.

Configure a Monitor Configuration

A monitor configuration defines what the Cloud Identity Engine collects from the cloud service provider and which segment receives the mappings. Configure one for monitoring purposes, such as audits, or to share IP address-to-tag mapping information with your firewalls using a segment.
There are four states for the connection to the cloud service provider:
  • Connected—The Cloud Identity Engine has successfully established a connection with the cloud service provider and can collect IP-tag mapping information.
  • Partially connected—The Cloud Identity Engine established a connection to some aspects of the configuration, such as the region for AWS, but not all of them. The Cloud Identity Engine receives IP-tag mappings from connected sources only.
  • Connection pending—The Cloud Identity Engine established a connection but has not completed the sync for the IP-tag mappings from one or more regions. For more information about the connection status, select Click to see details.
  • Not connected—The Cloud Identity Engine could not establish a connection with the cloud service provider using the current configuration.
  1. Select the Monitor & Status tab.
  2. Set Up a New Monitor Configuration and select the monitor configuration for the cloud service provider that you configured for the credential configuration.
  3. Enter a unique and descriptive Name for the configuration.
  4. Select the Credential Configuration that you configured.
  5. (AWS only) Optional Select the Role ARN you want to use.
  6. Select whether you want to configure the connection for All Regions, All VPCs (AWS only), or All Project IDs (GCP only).
    To select a specific region or virtual private cloud (VPC), deselect the All Regions or All VPCs check box, wait for the list of regions or VPCs to populate, and then select the region or VPC you want to include. To select a specific VPC, you must first select one or more regions, or select all regions.
  7. (Azure only) Select whether you want to Fetch Service Tags.
    Azure service tags simplify security for Azure virtual machines and Azure virtual networks because you can restrict network access to just the Azure services you want to use. A service tag represents a group of IP address prefixes for a particular Azure service. For example, a tag can represent all storage IP addresses.
  8. Optional To route IP-tag collection through a context collector deployed in an air-gapped or restricted environment, select a context collector or Context Collector Folder from the list of onboarded collectors.
    Selecting a folder routes collection through any context collector in that folder. If you do not select a collector, the Cloud Identity Engine collects IP-tag data directly from the cloud service provider.
  9. Define the Polling Interval (in seconds) to specify how frequently the Cloud Identity Engine checks for new data.
    The default is 60 seconds and the range is 60–1800 seconds.
  10. If you want to share the mappings, select the segment you configured. Otherwise, to create this configuration only for monitoring, without sending mappings to any firewalls, select None.
    If you need to change the segment after you submit the configuration, you must create a new configuration and select the segment you want to use.
  11. Submit the configuration.

Monitor and Manage Your Configurations

  1. Select the Monitor & Status tab.
  2. Use the filters to highlight the information you want to find.
    • Name—Enter the name of a configuration to filter results to that configuration. The search query does not need to be an exact match.
    • Vendor—Select the vendor type of the cloud service provider to filter the results to that vendor type.
    • Status—Select the status type, such as Connected or Partially Connected, to filter the results to that status type.
    • Segment—Select the segment name to view the monitor configurations that send mappings to that segment.
    • Associated Credential—Select the name of the credential configuration to view the monitor configurations that use it.
  3. Optional To remove the filter, click Reset.
  4. Optional To sync all new IP-tag mappings and use them in Security policy immediately, or to resolve any discrepancies in the IP-tag mappings, click Full Sync.
    The Sync Status displays the time and date of the last sync.
  5. Optional To change the IP-Tag Collection configuration, click Edit.
  6. Optional To remove the IP-Tag Collection configuration, click Delete and confirm the deletion.
    When you confirm the deletion, the Cloud Identity Engine removes all IP-tag mappings from the cloud service provider and from any firewalls that collect those mappings to enforce Security policy.

View IP Address-to-Tag Mappings

Options vary depending on your configuration type.
  1. Select the name of the configuration that you want to view from the IP-Tag Collection page.
  2. On the Monitor & Status page, review the Connection Details to view information such as the connection status.
  3. (AWS only) On the VPC tab, Search by VPC ID to view information for a specific VPC, or select the number in the IPs column to view the IP addresses associated with the VPC ID in that row.
  4. Select the Tag To IP tab and Search by Tag to view all IP addresses that contain the tag you specify.
    You can view the results for an exact or partial match for your query. You can optionally limit the search to a specific region or select All Regions.
  5. Select the number in the IPs column to view the IP addresses that the Cloud Identity Engine has collected for the selected Tag, then Search by IP Address.
    Close the window or click Cancel after you review the IP addresses.
  6. Select the IP To Tag tab to Search by IP Address.
    For an AWS-based configuration, you can also search by VPC ID.
  7. Click the number in the Tags column to view the tags associated with the IP Address of that row, then Search by Tag.
    Close the window or click Cancel after you review the tags.
Next steps: