--- 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 classic ELB Service # AWS classic 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 classic ELB Service discovery with Patterns This discovery pattern enables ServiceNow customers to identify and map AWS Classic Elastic Load Balancers (ELBs) that handle HTTP and HTTPS traffic within their cloud environments. ELB automatically distributes incoming application traffic across multiple targets, and this pattern supports top-down discovery using HTTP(s) or TCP endpoints as entry points. It integrates with Amazon EC2 instances to establish relationships between load balancers and backend servers. Show full answer Show less ServiceNow supports this discovery pattern on Jakarta or later releases and includes compatibility with Amazon Commercial Cloud Services (C2S), which is designed for government and intelligence community cloud environments. ## Prerequisites * Run a horizontal discovery using the Cloud API (CAPI) first, since this pattern depends on having load balancer data already stored in the Configuration Management Database (CMDB). * Create an application service in ServiceNow for each load balancer discovered. * Ensure read-only permissions are granted for specific AWS REST APIs related to describing load balancers and EC2 instances, necessary for retrieving load balancer details and their associated instances. * Download the Discovery and Service Mapping Patterns application from the ServiceNow Store to enable the pattern. * Install and configure the MID Server on a host that meets ServiceNow's system requirements to enable secure communication and discovery execution. * Verify REST API permissions using the Cloud Discovery patterns spreadsheet for up-to-date user permissions and pattern information. ## Key Features * Supports discovery of Classic ELBs handling HTTP and HTTPS traffic using top-down discovery methods. * Automatically establishes relations between load balancers and backend Amazon EC2 instances. * Collects detailed configuration data such as fully qualified domain names (FQDN), ports, IP addresses, and protocols for load balancers and instances. * Enables integration with ServiceNow's CMDB and application service mapping for comprehensive visibility into AWS load balancing infrastructure. * Supports discovery in government cloud environments via Amazon C2S. ## Data Collected The discovery process populates CMDB tables with critical information, including: * **Load Balancer Services \[cmdbcilbservice\]**: FQDN, load balancer name with port, various port details (frontend, backend, server), protocol, and IP address. * **IP Address \[cmdbciipaddress\]**: IP addresses associated with the load balancer FQDN and relevant network details such as netmask. ## Practical Benefits By implementing this discovery pattern, ServiceNow customers gain automated and accurate visibility into their AWS Classic ELB infrastructure, enabling better service mapping, impact analysis, and cloud governance. It simplifies maintaining up-to-date CMDB data, which supports operational efficiency and informed decision-making for cloud resource management. Discovery uses the Amazon AWS classic ELB Service discovery pattern to find all load balancers that use HTTP and HTTPS traffic. Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple targets. The Amazon AWS classic ELB Service discovery pattern supports top-down discovery. The two possible entry points for top-down discovery are the HTTP(s) Endpoint and TCP 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 Jakarta 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-classic-elb-service-discovery__section_fyy_mbf_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.\.amazonaws.com/?Action=DescribeLoadBalancers\&Version=2012-06-01\&LoadBalancerNames.member.1=\ * https://ec2.\.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=\ (to create relation between LB and EC2 instance) {#aws-classic-elb-service-discovery__ul_jfp_why_vjb} * 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-classic-elb-service-discovery__ul_rs4_sbf_wjb} ## Verify the REST API permissions {#aws-classic-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-classic-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-classic-elb-service-discovery__section_vh4_sdf_wjb} The discovered data includes the following tables and fields. {#aws-classic-elb-service-discovery__table_otp_vdf_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: \:\. | | Back End Port \[back_end_port\] | Port of the instance. | | Server Port \[server_port\] | Port of the instance. | | Port \[port\] | Port of the load balancer. | | Front End Port \[front_end_port\] | Port of the load balancer. | | Object ID \[object_id\] | LB port. | | IP Address \[ip_address\] | IP address of the FQDN. | | Server Protocol \[server_protocol\] | Protocol of the instance. | | IP Address \[cmdb_ci_ip_address\] || | IP Address \[ip_address\] | IP address of the load balancer FQDN. | | Name \[name\] | Name of the load balancer, in the following format: \:\. | | Netmask \[netmask\] | 0.0.0.0 | [ ] {#aws-classic-elb-service-discovery__table_otp_vdf_wjb}