--- 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 VPC Managed Prefix List # Amazon Amazon VPC Managed Prefix List pattern-based discovery {#ariaid-title1} Release version: Australia Updated May 13, 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 VPC Managed Prefix List pattern-based discovery This pattern in the Discovery and Service Mapping Patterns application enables ServiceNow customers to discover Amazon Virtual Private Cloud (Amazon VPC) Managed Prefix Lists within their AWS environments. It helps populate detailed data about these resources into both CMDB and non-CMDB tables, supporting effective cloud resource management and visibility. Show full answer Show less To use this pattern, customers must meet AWS discovery prerequisites, ensure relevant resources are not excluded via the Resource Inclusion List, and enable the pattern since it is disabled by default. ## Key Features * **Pattern Activation:** Starting with Visibility Content 6.28.0, enabling or disabling this pattern is not considered a customization, ensuring updates continue seamlessly after upgrades. * **Data Population:** The pattern populates data into two main areas: * **Non-CMDB Tables:** Data such as managed prefix list details are stored when running the "Amazon AWS - VPC Managed Prefix List - Extended Inventory (LP)" pattern, accessible under AWS configuration in ServiceNow. * **CMDB Tables:** Relevant configuration items representing managed prefix lists are created with detailed fields like name, ARN, resource type, install status, and operational status. * **CI Relationships and References:** The pattern automatically defines relationships such as "Hosted on" linking managed prefix lists to AWS Datacenters, and references between CMDB tables that maintain data integrity and context. * **Tag Discovery:** AWS tags associated with prefix lists are collected and stored in the Key Value \[cmdbkeyvalue\] table, enabling enhanced resource categorization and filtering. ## Practical Impact for ServiceNow Customers By implementing this discovery pattern, customers gain comprehensive and automated visibility into their Amazon VPC Managed Prefix Lists, including their metadata, operational status, and cloud relationships. This supports accurate CMDB population, improved cloud resource tracking, and better integration with AWS infrastructure components. Customers should verify prerequisite configurations, remove any resource exclusions that might prevent discovery, and enable the pattern to ensure up-to-date and consistent discovery results. The automatic handling of tags and relationships further enhances the usability and manageability of discovered cloud resources within ServiceNow. Discovery and Service Mapping Patterns finds Amazon Virtual Private Cloud (Amazon VPC) Managed Prefix Lists 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-vpc-managed-prefix-list__section_rpj_fj2_bgc} 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-vpc-managed-prefix-list__activating-disabled-pattern-not-customization} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables. ## Data stored in non-CMDB tables {#aws-vpc-managed-prefix-list__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Amazon AWS - VPC Managed Prefix List - 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-vpc-managed-prefix-list__table_non_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the managed prefix list. | | Object ID \[object_id\] | The Amazon Resource Name (ARN) of the managed prefix list. | | List ID \[list_id\] | The unique identifier of the managed prefix list. | | State \[state\] | The current state of the managed prefix list. For example: create-complete, modify-in-progress, or delete-complete. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 1. AWS VPC Managed Prefix List \[cmdb_aws_vpc_managed_prefix_list\]] {#aws-vpc-managed-prefix-list__table_non_cmdb} ## Data stored in CMDB tables {#aws-vpc-managed-prefix-list__section_ggp_ql2_bgc} Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - VPC Managed Prefix List - Extended Inventory (LP) pattern. {#aws-vpc-managed-prefix-list__table_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the managed prefix list. | | Object ID \[object_id\] | The ARN of the managed prefix list. | | Resource type \[resource_type\] | Type of resource. The value is set to AWS::VPC::ManagedPrefixList. | | 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. | [Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]] {#aws-vpc-managed-prefix-list__table_cmdb} ## CI relationships {#aws-vpc-managed-prefix-list__section_dc4_ghc_dgc} The Amazon AWS - VPC Managed Prefix List - Extended Inventory (LP) pattern creates the following relationships and references to support Amazon VPC Managed Prefix List discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#aws-vpc-managed-prefix-list__table_relationships__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 3. CI relationships] {#aws-vpc-managed-prefix-list__table_relationships} {#aws-vpc-managed-prefix-list__table_ci_references__entry__3} | CI | Field | Referenced CI | |-|-|-| | AWS VPC Managed Prefix List \[cmdb_aws_vpc_managed_prefix_list\] | Configuration Item \[configuration_item\] | Cloud Resource \[cmdb_ci_cmp_resource\] | | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud Resource \[cmdb_ci_cmp_resource\] | [Table 4. CI references] {#aws-vpc-managed-prefix-list__table_ci_references} ## AWS Tag discovery {#aws-vpc-managed-prefix-list__section_lyw_zhc_dgc} The Amazon AWS - VPC Managed Prefix List - Extended Inventory (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-vpc-managed-prefix-list__table_ojy_vss_5hc__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | | Configuration item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 5. Key Value \[cmdb_key_value\]] {#aws-vpc-managed-prefix-list__table_ojy_vss_5hc} *[\>]: and then