---
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


---

# AWS application ELB Service

# AWS application ELB Service discovery with Patterns {#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 AWS application ELB Service discovery with Patterns

The AWS application ELB Service discovery pattern in ServiceNow enables customers to discover and map all Elastic Load Balancers (ELBs) within their AWS environment using top-down discovery.
ELB automatically distributes application traffic across multiple targets and supports advanced features such as ultra-high performance, TLS offloading, centralized certificate deployment, UDP support, and static IP addresses.
Show full answer Show less  
This pattern works by starting discovery at the HTTP(s) endpoint and tracing outgoing relations to Amazon EC2 instances. It supports the Amazon Commercial Cloud Services (C2S) environment and requires ServiceNow Kingston or later releases.

## Prerequisites and Setup

* Run a horizontal discovery first using Cloud API (CAPI), as this pattern only supports top-down discovery.
* Ensure load balancer data is stored in the Configuration Management Database (CMDB) and create an application service for each load balancer.
* Set read-only permissions for specific AWS ELB and EC2 REST APIs required for discovery, covering load balancers, listeners, rules, target group health, and instance descriptions.
* Download and install the Discovery and Service Mapping Patterns from the ServiceNow Store.
* Install the MID Server on a host machine meeting ServiceNow's system requirements to enable discovery.
* Verify REST API permissions using the Cloud Discovery patterns spreadsheet, which details necessary user permissions, pattern names, CI classes, and vendor documentation links.
* Optionally, test AWS REST APIs with tools like Postman for validation before discovery runs.

## Data Collected During Discovery

The discovery process collects detailed information about load balancers, which is stored in the **Load Balancer Services \[cmdbcilbservice\]** table in the CMDB. Key fields include:

* **Fully Qualified Domain Name (fqdn):** DNS name of the load balancer.
* **Name:** Load balancer name formatted as \<LB name\>:\<LB port\>.
* **Serial Number:** Formatted as ##ObjectID=\<LBARN\> to uniquely identify the load balancer.
* **Port:** Port number the load balancer listens on.
* **Object ID:** Unique identifier for the load balancer.
* **IP Address:** IP address corresponding to the FQDN.

## Benefits for ServiceNow Customers

This discovery pattern helps ServiceNow customers achieve accurate and comprehensive visibility into AWS ELB infrastructure, enabling better management, mapping, and governance of application traffic routing. By integrating ELB data into the CMDB, customers can enhance service mapping, impact analysis, and operational efficiency within their cloud environments.  
Discovery uses the Amazon AWS application ELB Service discovery pattern
to show all load balancers in your environment in a map.
Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple targets.  
The Amazon AWS application ELB Service discovery pattern supports top-down discovery. This pattern discovers all load balancers with these characteristics:

* Use ultra-high performance, TLS offloading at scale, and centralized certificate deployment
* Support UDP and static IP addresses for your application
{#aws-application-elb-service-discovery__ul_gjs_psf_wjb}

For top-down discovery, the entry point is HTTP(s) Endpoint. Outgoing relations are to Amazon EC2 instances.

The ServiceNow AI Platform supports Amazon Commercial Cloud Services (C2S) for discovery and cloud governance. C2S is the government program that brings AWS into the Intelligence Community.

You can use this pattern on the ServiceNow platform using Kingston or later releases.
Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).

## Prerequisites {#aws-application-elb-service-discovery__section_hyx_g5f_wjb}

* Run a horizontal discovery, using [Cloud API (CAPI)](https://www.servicenow.com/docs/eNB4YRBFj~nEtww3DT5e_Q "The Cloud API (CAPI) enables you to integrate Cloud Provisioning and Governance with cloud providers using REST APIs."). This is necessary because this discovery pattern supports top-down discovery only. For Cloud Discovery, you can run the horizontal discovery as usual.
* When the load balancers data has been stored in the Configuration Management Database (CMDB), create an application service for each load balancer.
* Set read-only permissions for these REST APIs:
  * https://elasticloadbalancing.\<REGION\>.amazonaws.com/?Action=DescribeLoadBalancers\&LoadBalancerArns.member.1=\<LB_ARN\>\&Version=2015-12-01
  * https://elasticloadbalancing.\<REGION\>.amazonaws.com/?Action=DescribeLoadBalancers\&Version=2015-12-01
  * https://elasticloadbalancing.\<REGION\>.amazonaws.com/?Action=DescribeListeners\&LoadBalancerArn=\<LB_ARN\>\&Version=2015-12-01
  * https://elasticloadbalancing.\<REGION\>.amazonaws.com/?Action=DescribeRules\&ListenerArn=\<LISTENER_ARN\>\&Version=2015-12-01
  * https://elasticloadbalancing.\<REGION\>.amazonaws.com/?Action=DescribeTargetHealth\&TargetGroupArn=\<TARGET_GROUP_ARN\>\&Version=2015-12-01
  * https://ec2.\<REGION\>.amazonaws.com/?Action=DescribeInstances\&Version=2016-11-15\&Filter.1.Name=instance-state-name\&Filter.1.Value=running\&Filter.2.Name=instance-id\&Filter.2.Value=\<INSTANCE_ID\>
  {#aws-application-elb-service-discovery__ul_rys_l5f_wjb}
* For Cloud Discovery, download the Discovery and Service Mapping Patterns from the ServiceNow Store.
* When installing the MID Server, ensure that the host machine meets or exceeds the [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) published on the ServiceNow documentation site.
{#aws-application-elb-service-discovery__ul_f2c_35f_wjb}

## Verify the REST API permissions {#aws-application-elb-service-discovery__id_ysv_22b_f1c}

Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#aws-application-elb-service-discovery__cloud-discovery-api-ph-short-prereq}
Note:  
You can test the AWS REST APIs using Postman API platform. For more information, see the [How to test AWS REST API using POSTMAN \[KB0782183\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0782183) article in the Now Support Knowledge Base.

## Data collected by Discovery during horizontal discovery {#aws-application-elb-service-discovery__section_i5j_s5f_wjb}

The discovered data includes the following tables and fields.
{#aws-application-elb-service-discovery__table_sf5_w5f_wjb__entry__2}

| Table and field | Description |
|-|-|
| Load Balancer Services \[cmdb_ci_lb_service\] ||
| Fully qualified domain name \[fqdn\] | Fully Qualified Domain Name (FQDN) of the load balancer. The DNS name. |
| Name \[name\] | Name of the load balancer, in the following format: \<LB name\>:\<LB port\>. |
| Serial Number \[serial_number\] | Serial number of the load balancer, in the following format: ##Object_ID=\<LB_ARN\>. |
| Port \[port\] | Port of the load balancer. |
| Object ID \[object_id\] | Unique identifier of the load balancer. |
| IP Address \[ip_address\] | IP address of the FQDN. |
[ ]

{#aws-application-elb-service-discovery__table_sf5_w5f_wjb}