--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Amazon EC2 VPC Peering Connection # Amazon EC2 VPC Peering Connection pattern-based discovery {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Amazon EC2 VPC Peering Connection pattern-based discovery This pattern-based discovery enables ServiceNow customers to identify and map Amazon EC2 VPC Peering Connections within their AWS cloud environments using the Discovery and Service Mapping Patterns application. It requires meeting AWS discovery prerequisites and configuring specific settings to ensure accurate data collection, which is then populated into both CMDB and non-CMDB tables. This discovery supports comprehensive visibility and management of VPC peering connections within ServiceNow's Configuration Management Database (CMDB). Show full answer Show less ## Key Features * **Prerequisites and Setup:** Verify AWS discovery prerequisites, remove relevant resources from the Resource Inclusion List to avoid duplication, and enable the Amazon EC2 VPC Peering Connection pattern (disabled by default). * **Pattern Activation and Updates:** From Visibility Content version 6.28.0 onward, enabling or disabling patterns is not considered customization, allowing automatic updates while preserving activation status after upgrades. * **Support for AWS GovCloud:** Requires using a datacenter URL when configuring AWS service accounts for GovCloud regions. * **Data Population:** Discovery populates data in: * **Non-CMDB Tables:** Using the "Amazon AWS - Elastic Compute Cloud VPC Peering Connection - Extended Inventory (LP)" pattern, data is stored in AWS-specific non-CMDB tables accessible via ServiceNow navigation. * **CMDB Tables:** Key information about VPC Peering Connections is stored in the `cmdbawselasticcomputecloudvpcpeeringconnection` and `cmdbcicloudgateway` tables, including unique ARNs, status, and resource descriptions. * **CI Relationships:** The pattern automatically creates relationships between Cloud Gateway CIs and AWS Datacenter CIs to accurately represent hosting and references within the CMDB. * **AWS Tag Discovery:** Tags associated with VPC Peering Connections are collected and stored in the `cmdbkeyvalue` table for enhanced resource categorization and filtering. ## What You Can Expect By implementing this discovery pattern, ServiceNow customers gain automated detection and mapping of AWS VPC Peering Connections, enabling better management and operational insight within their CMDB. This facilitates improved cloud infrastructure visibility, relationship tracking, and easier compliance and governance of AWS networking resources. Additionally, support for GovCloud regions and automatic pattern updates streamline ongoing maintenance and accuracy of cloud asset data. Discovery and Service Mapping Patterns finds AWS services on your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Pattern-based discovery and mapping requirements {#aws-ec2-vpc-peering-connection__selection_ipy_53n_jfc} Verify the AWS discovery prerequisites : For more information, see the prerequisites section in [AWS discovery using patterns](https://www.servicenow.com/docs/NFaTlkGaSxMWb2bQPsCnCA "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). Remove resources from the Resource Inclusion List table : Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource Inclusion List, see [AWS Resource Inventory discovery with Patterns](https://www.servicenow.com/docs/0pDNq0441mpy~sExfQvvqA "The ServiceNow Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). Enable the relevant pattern : The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#aws-ec2-vpc-peering-connection__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud : Discovering AWS GovCloud (US) accounts requires using a datacenter URL when setting up an AWS service account. For more information, see [Create AWS service accounts](https://www.servicenow.com/docs/vpueuFRHMWLNi6dzsJv94A "Create AWS service accounts on the ServiceNow AI Platform to access your AWS account during AWS discovery."). Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables. ## Data stored in non-CMDB tables {#aws-ec2-vpc-peering-connection__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Amazon AWS - Elastic Compute Cloud VPC Peering Connection - Extended Inventory (LP) pattern. You can review the non-CMDB AWS tables by navigating to AllConfigurationAWS. You can also search the navigation filter for the specific pattern name. {#aws-ec2-vpc-peering-connection__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Object Id \[object_id\] | The Amazon Resource Name (ARN) uniquely identifying the VPC Peering Connection. The ARN consists of the region, account ID, and VPC ID in the following format: arn:aws:ec2:\:\:vpc-peering-connection/\. | | Name \[name\] | The unique identifier of the VPC involved in the peering connection. | | Status \[status\] | The current status of the VPC peering connection. | | Configuration Item \[configuration_item\] | References the Cloud Gateway \[cmdb_ci_cloud_gateway\] table. | [Table 1. AWS Elastic Compute Cloud - VPC Peering Connection \[cmdb_aws_elastic_compute_cloud_vpc_peering_connection\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - Elastic Compute Cloud VPC Peering Connection - Extended Inventory (LP) pattern. {#aws-ec2-vpc-peering-connection__entry__12} | Field | Description | |-|-| | Object ID \[object_id\] | The ARN uniquely identifying the VPC Peering Connection. The ARN consists of the region, account ID, and VPC ID in the following format: arn:aws:ec2:\:\:vpc-peering-connection/\. | | Name \[name\] | The unique identifier of the VPC involved in the peering connection. | | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | | Description \[short_description\] | Type of resource. The value is set to AWS::EC2::VPCPeeringConnection. | [Table 2. Cloud Gateway \[cmdb_ci_cloud_gateway\]] ## CI relationships The Amazon AWS - Elastic Compute Cloud VPC Peering Connection - Extended Inventory (LP) pattern creates these relationships to support Amazon EC2 VPC Peering Connection discovery. {#aws-ec2-vpc-peering-connection__entry__25} | CI | Relationship | CI | |-|-|-| | Cloud Gateway \[cmdb_ci_cloud_gateway\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | AWS Elastic Compute Cloud - VPC Peering Connection \[cmdb_aws_elastic_compute_cloud_vpc_peering_connection\] | References | Cloud Gateway \[cmdb_ci_cloud_gateway\] | [ ] ## AWS tag discovery {#aws-ec2-vpc-peering-connection__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-ec2-vpc-peering-connection__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#aws-ec2-vpc-peering-connection__table_axq_spc_y2c} *[\>]: and then