--- 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 --- # AWS Application and Network LB # AWS Application and Network LB pattern-based discovery {#ariaid-title1} * Release version: Yokohama * * Updated June 15, 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 AWS Application and Network LB pattern-based discovery The AWS Application and Network LB pattern-based discovery in ServiceNow enables automated identification and mapping of AWS Application Load Balancers (ALBs) and Network Load Balancers (NLBs) within your cloud environment. This capability is part of the Discovery and Service Mapping Patterns application, which may require updating to the latest version from the ServiceNow Store to ensure full functionality. Show full answer Show less ## Key Features * **Discovery Prerequisites:** Customers must verify AWS discovery prerequisites and configure Discovery schedules properly, particularly when working with AWS GovCloud (US) accounts, which require specific datacenter URL configurations. * **Data Collection:** The discovery process populates detailed load balancer data into the CMDB, including attributes such as name, IP address, Amazon Resource Name (ARN), DNS name, hosted zone details, state, and descriptive identifiers. * **CI Relationships:** The pattern establishes essential relationships between the load balancer and related configuration items such as cloud subnets, availability zones, AWS datacenters, DNS names, and compute security groups to provide a comprehensive view of the infrastructure. * **AWS Tag Discovery:** Tags associated with load balancers are collected and stored in the Key Value \[cmdbkeyvalue\] table, allowing tagging data to be integrated with CMDB records for improved governance and management. ## Key Outcomes * Accurate and automated discovery of AWS Application and Network Load Balancers integrated into the ServiceNow CMDB. * Comprehensive visibility into load balancer configurations, states, and network relationships, supporting effective cloud infrastructure management. * Enhanced tracking and management of AWS resource metadata through tag collection, facilitating governance and operational insights. * Support for AWS GovCloud discovery scenarios with appropriate configuration guidance. Discovery and Service Mapping Patterns finds AWS Application Load Balancers and Network Load Balancers 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-application-network-lb-pattern__section_rpj_fj2_bgc} 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."). 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."). ## Data collected by Discovery during horizontal discovery {#aws-application-network-lb-pattern__section_ggp_ql2_bgc} Discovery populates the data in the CMDB when running the Amazon AWS - Application and Network LB (LP) pattern. {#aws-application-network-lb-pattern__table_lb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the load balancer. | | Fully Qualified Domain Name \[fqdn\] | IP address of the fully qualified domain name (FQDN) of the load balancer. | | Object ID \[object_id\] | The Amazon Resource Name (ARN) of the load balancer. | | DNS Name \[dns_name\] | The public Domain Name System (DNS) name of the load balancer. | | Canonical Hosted Zone Name \[canonical_hosted_zone_name\] | The name of the Amazon Route 53 hosted zone associated with the load balancer. | | Canonical Hosted Zone ID \[canonical_hosted_zone_id\] | The ID of the Amazon Route 53 hosted zone associated with the load balancer. | | State \[state\] | The state of the load balancer. | | Short Description \[short_description\] | A concatenation of the series of attributes for the load balancer, including LB ARN, VPC ID, type, and zone. | | Comments \[comments\] | Identifier for internal usage (deletion strategy). | [Table 1. Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\]] {#aws-application-network-lb-pattern__table_lb} {#aws-application-network-lb-pattern__table_dns__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the DNS. | | Object ID \[object_id\] | Name of the DNS. | | IP Address \[ip_address\] | IP address of the DNS. | | Comments \[comments\] | Identifier for internal usage (deletion strategy). | [Table 2. DNS Name \[cmdb_ci_dns_name\]] {#aws-application-network-lb-pattern__table_dns} ## CI relationships {#aws-application-network-lb-pattern__section_dc4_ghc_dgc} The Amazon AWS - Application and Network LB (LP) pattern creates the following relationships and references to support AWS Application and Network LB discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#aws-application-network-lb-pattern__table_bkg_jhc_dgc__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Subnet \[cmdb_ci_cloud_subnet\] | Contains::Contained by | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | | Availability Zone \[cmdb_ci_availability_zone\] | Contains::Contained by | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Contains::Contained by | DNS Name \[cmdb_ci_dns_name\] | | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Contains::Contained by | Compute Security Group \[cmdb_ci_compute_security_group\] | [Table 3. CI relationships] {#aws-application-network-lb-pattern__table_bkg_jhc_dgc} {#aws-application-network-lb-pattern__table_ci_references__entry__3} | CI | Field | Referenced CI | |-|-|-| | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | [Table 4. CI references] {#aws-application-network-lb-pattern__table_ci_references} ## AWS Tag discovery {#aws-application-network-lb-pattern__section_lyw_zhc_dgc} The Amazon AWS - Application and Network LB (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-application-network-lb-pattern__table_ojy_vss_5hc__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | | Configuration item \[configuration_item\] | References the Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] table. | [Table 5. Key Value \[cmdb_key_value\]] {#aws-application-network-lb-pattern__table_ojy_vss_5hc}