--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama 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: Yokohama * * Updated August 11, 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 The Amazon EC2 VPC Peering Connection pattern-based discovery in ServiceNow's Discovery and Service Mapping Patterns enables automated detection and mapping of AWS VPC peering connections within your cloud environment. This pattern helps you populate relevant configuration items (CIs) and associated data into your CMDB and non-CMDB tables, facilitating comprehensive cloud infrastructure visibility and management. Show full answer Show less ## Key Features * **Pattern Activation:** The VPC Peering Connection pattern is disabled by default and must be enabled to start discovery. Activating or deactivating patterns no longer counts as customization from version 6.28.0 onwards, ensuring patterns stay up to date. * **Prerequisites and Setup:** Ensure AWS discovery prerequisites are met, including removing the VPC peering connection resource from the Resource Inclusion List to avoid duplicate discovery. For GovCloud accounts, configure discovery schedules with the appropriate datacenter URLs. * **Data Population:** Discovered data is stored both in CMDB tables (such as Cloud Gateway \[cmdbcicloudgateway\]) and non-CMDB tables (such as AWS Elastic Compute Cloud VPC Peering Connection \[cmdbawselasticcomputecloudvpcpeeringconnection\]). This supports detailed inventory and relationship mapping. * **CI Relationships:** The discovery pattern establishes relationships, linking the VPC Peering Connection CI to Cloud Gateway and AWS Datacenter CIs, supporting accurate service mapping and dependency visualization. * **Tag Collection:** AWS tags associated with VPC peering connections are collected and stored in the Key Value \[cmdbkeyvalue\] table, aiding in categorization and filtering within the CMDB. ## Key Outcomes * **Accurate Cloud Asset Visibility:** Automatically discover and track AWS VPC peering connections, including status and identifiers, providing an up-to-date and detailed cloud infrastructure inventory. * **Improved CMDB Data Quality:** Populate structured data with unique identifiers (ARNs), statuses, and relationships, enabling better governance and impact analysis. * **Enhanced Cloud Service Mapping:** Establish CI relationships that support comprehensive service maps and dependency views for AWS cloud environments. * **Tag-based Management:** Leverage AWS tagging information within ServiceNow to refine asset management, reporting, and automation workflows. Discovery and Service Mapping Patterns finds AWS services on your cloud environment. Discovering some of these resources may 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 [Amazon AWS Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/nnBwzYmMo_kpTZpG3y5~xQ "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources may 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 [Amazon Web Services (AWS) Resource Inventory](https://servicenow-prod.fluidtopics.net/U2bwxjeyIbyEXySOOJQkYA "The ServiceNow Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources may 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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/CvTA68TY3ph_FRR49RbdPg "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