--- 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 cloud components # Amazon AWS Cloud components discovery using patterns {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 26 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 AWS Cloud components discovery using patterns This guide covers how ServiceNow Discovery and Service Mapping Patterns enable automated discovery of Amazon AWS Cloud components during horizontal discovery. It is designed for ServiceNow customers managing AWS environments, detailing prerequisites, configuration steps, discovered Configuration Items (CIs), relationships, and supported AWS services. The patterns leverage AWS APIs and IAM roles to discover resources efficiently and populate the CMDB accurately. Show full answer Show less ## Prerequisites and Setup * **Application Updates:** Ensure Discovery and Service Mapping Patterns and CMDB CI Class Models are up to date, ideally from the ServiceNow Store. * **Cloud Provisioning Update:** If using Cloud Provisioning and Governance, update the `getOperationGR(type)` method to improve AWS CloudFormation Template stack discovery. * **Activate CI Relationships:** Enable CI relationships used in tag-based discovery (available from version 1.0.68) to integrate discovered AWS components into service instances. * **AWS Service Accounts:** Set up AWS Management Console service accounts, especially management accounts for AWS Organizations, to simplify member account discovery. * **Credentials Management:** Use dynamically acquired credentials for member accounts or configure MID Server with IAM roles and proper IAM user policies granting read-only access to necessary AWS resources. * **Discovery Schedule:** Create an AWS Discovery schedule within the Discovery Admin Workspace. * **Optimize Discovery:** Starting with version 1.29.0, discovery can be limited to AWS datacenters containing active resources by adjusting the `mid.cloud.discovery.sonar.discoverallawsdatacenters` MID Server property to `false`. * **REST API Permissions:** Grant permissions for using AWS REST APIs during discovery, with a regularly updated spreadsheet available to track required permissions and patterns. * **China Region Support:** Discovery supports AWS services in the China region with specific datacenter URLs and considerations. ## Discovery Model and Data Collection The discovery process identifies AWS datacenters (regions) with resources ("active"), without resources ("passive"), or inaccessible ("empty"). Only active or empty datacenters are scanned during discovery to improve efficiency. Discovered AWS components are categorized into various CI classes such as Availability Zones, Load Balancers, Hosts, Networks, Subnets, Storage Volumes, Security Groups, and many more, each with relevant attributes like names, IDs, states, and relationships. ## Key Discovered Configuration Items (CIs) * **Compute Resources:** Instances, Hosts, Virtual Machines, and Cloud System Management Agents (e.g., AWS SSM Agents). * **Networking:** VPC Networks, Subnets, Internet Gateways, NAT Gateways, Route Tables, and Security Groups. * **Load Balancers:** Classic, Application, and Network Load Balancers, including associated pools, services, pool members, and IP addresses. * **Storage:** Storage Volumes with state and type details. * **Organizational Units and Accounts:** Cloud Organizations, AWS Organizational Units, and Cloud Service Accounts. * **Security and Access:** Web ACLs, Customer Gateways, VPN Connections, and VPN Gateways. ## CI Relationships and Mapping The patterns automatically create relationships between CIs to reflect real-world AWS infrastructure connections. Examples include: * Datacenters containing Availability Zones. * Load Balancers hosting services and owning pools and IP addresses. * Hosts running on Datacenters and hosting various network and security components. * Organizational Units contained within Cloud Organizations and owning service accounts. * Storage Volumes contained by Availability Zones and hosted on Datacenters. These relationships support accurate service maps and dependency views within ServiceNow. ## Events and Services Discovery Discovery reacts to AWS events indicating state changes in components, triggering pattern-based re-discovery for components such as EC2 instances, security groups, subnets, networks, storage volumes, and load balancers. This ensures CMDB data remains current and reflects actual AWS environments. ## Practical Benefits for ServiceNow Customers * **Automated, comprehensive discovery** of AWS cloud components ensures your CMDB accurately reflects your AWS environment. * **Optimized discovery performance** by focusing on datacenters with active resources, reducing unnecessary API calls and discovery time. * **Integrated service mapping** through tag-based discovery and CI relationships enhances visibility into cloud service dependencies. * **Support for multi-account AWS Organizations** simplifies credential management and expands discovery scope. * **Support for AWS regions including China** accommodates global AWS deployments. * **Extensive CI classes and relationships** provide rich, actionable data for IT operations, security, and compliance teams. ## Next Steps\https://organizations.cn-northwest-1.amazonaws.com.cn. * To learn more about AWS master account and sub-account support in the China region, see [KB1704526](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704526). * To identify AWS patterns supported in the China region, refer to the Cloud Discovery patterns spreadsheet. The AWS China Region Support column has a Yes value for supported patterns. {#data-discovered-aws-patterns__ul_zqf_qtn_1dc} ## AWS resources discovery by datacenters {#data-discovered-aws-patterns__active-datacenter-discovery} Starting with version 1.29.0, Discovery and Service Mapping Patterns introduces a new AWS datacenter discovery model. The previous model discovered all datacenters, regardless of whether they contained relevant resources. The new model improves the AWS discovery performance by focusing on only datacenters that contain resources. AWS has multiple datacenters around the world, but resources like load balancers and virtual machines are typically deployed in only some of them. The Amazon AWS Datacenter Discovery pattern runs before all other AWS patterns to identify datacenters with resources related to your service account ("active") and those without ("passive"). A datacenter can also be classified as "empty" due to API call errors, AWS Config service not being enabled, or permission issues. You can check the discovery log for the exact cause of the error. For more information, see [Logs for horizontal discovery](https://servicenow-prod.fluidtopics.net/ao5OrQtRxbDaPsjhkL2QeA#r_DiscoveryLog "The system collects logs to reflect the activity that takes place during a horizontal discovery based on both patterns and probes. Use the logs to fine-tune or troubleshoot the discovery process."). After identifying "active", "passive", or "empty" datacenters, the discovery schedule continues to execute all AWS patterns only for "active" or "empty" datacenters, to discover your AWS cloud resources. "Passive" datacenters are ignored during the schedule. The Refresh Datacenters flow continues to display all regions, not just active ones. You don't need to create another schedule when a resource is added or a datacenter switches from passive to active. You might notice differences in the AWS discovery log, in discovery time and in the CMDB, depending on the service account and MID Server property settings. Datacenters that have already been discovered before upgrading to Discovery and Service Mapping Patterns version 1.29.0 remain in the Amazon AWS Datacenters table. The mid.cloud.discovery.sonar.discover_all_aws_datacenters MID Server property is set to true by default, which discovers all datacenters. To limit discovery to the "active" or "empty" datacenters, set this property to false. For information on setting up active datacenter discovery, see the (optional) Optimize discovery by including only datacenters with resources prerequisite. {#data-discovered-aws-patterns__table_wzt_31d_dhc__entry__3} | MID Server property setting | Flow | Discovered/displayed datacenters | |-|-|-| | False | New schedule | All datacenters except passive | | False | Refresh Datacenters | All datacenters | | True (default) | New schedule | All datacenters | | True (default) | Refresh Datacenters | All datacenters | [Table 1. Differences in datacenter discovery by mid.cloud.discovery.sonar.discover_all_aws_datacenters MID Server property setting] {#data-discovered-aws-patterns__table_wzt_31d_dhc} Figure 1. AWS datacenter model flow by mid.cloud.discovery.sonar.discover_all_aws_datacenters MID Server property setting ## Data collected by Discovery during horizontal discovery {#data-discovered-aws-patterns__section_e1d_bfm_kmb} Resources discovered using the Amazon AWS - Availability Zone (LP) pattern : {#data-discovered-aws-patterns__table_erd_wrw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Availability Zone. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | State \[state\] | The state of the Availability Zone. The possible values are: available, information, impaired, and unavailable. | [Table 2. Availability Zone \[cmdb_ci_availability_zone\]] {#data-discovered-aws-patterns__table_erd_wrw_mdc} Resources discovered using the Amazon AWS - Classic LB (LP) pattern : {#data-discovered-aws-patterns__table_h3y_1sw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the load balancer. | | Fully Qualified Domain Name \[fqdn\] | The DNS name of the load balancer. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | DNS Name \[dns_name\] | The DNS name of the load balancer. | | Canonical Hosted Zone Name \[canonical_hosted_zone_name\] | The DNS name of the load balancer. | | Canonical Hosted Zone ID \[canonical_hosted_zone_id\] | The ID of the Amazon Route 53 hosted zone for the load balancer. | [Table 3. Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\]] {#data-discovered-aws-patterns__table_h3y_1sw_mdc} {#data-discovered-aws-patterns__table_o55_bsw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | IP address of the Load Balancer. | | Object ID \[object_id\] | IP address of the Load Balancer. | | IP Address \[ip_address\] | IP address of the Load Balancer. | | Comments \[comments\] | Comments related to the Configuration Item (CI). | [Table 4. Cloud LB IPAddress \[cmdb_ci_cloud_lb_ipaddress\]] {#data-discovered-aws-patterns__table_o55_bsw_mdc} {#data-discovered-aws-patterns__table_t1w_bsw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Domain Name System (DNS). | | IP Address \[ip_address\] | IP address of the DNS. | | Comments \[comments\] | Comments related to the CI. | [Table 5. DNS Name \[cmdb_ci_dns_name\]] {#data-discovered-aws-patterns__table_t1w_bsw_mdc} {#data-discovered-aws-patterns__table_w1x_bsw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the load balancer pool. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | Comments \[comments\] | Comments related to the CI. | [Table 6. Load Balancer Pool \[cmdb_ci_lb_pool\]] {#data-discovered-aws-patterns__table_w1x_bsw_mdc} {#data-discovered-aws-patterns__table_zzx_bsw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the load balancer pool member (known in AWS as a target). | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | [Table 7. Load Balancer Pool Member \[cmdb_ci_lb_pool_member\]] {#data-discovered-aws-patterns__table_zzx_bsw_mdc} {#data-discovered-aws-patterns__table_a1z_bsw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the load balancer service. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | Port \[port\] | The port on which the load balancer is listening. | | Service Port \[service_port\] | The port on which the instance is listening. | | Server Protocol \[service_protocol\] | The protocol to use for routing traffic to instances: HTTP, HTTPS, TCP, or SSL. | | Listener Protocol \[service_protocol\] | The load balancer transport protocol to use for routing: HTTP, HTTPS, TCP, or SSL. | | Comments \[comments\] | Comments related to the CI. | [Table 8. Load Balancer Service \[cmdb_ci_lb_service\]] {#data-discovered-aws-patterns__table_a1z_bsw_mdc} Resources discovered using the Amazon AWS - LB Pool Member(LP) pattern : {#data-discovered-aws-patterns__table_ntq_x3y_p2c__entry__2} | Field | Description | |-|-| | Name \[name\] | Target ID, depending on the target type. For example: Instance ID, IP address, Lambda ARN, or Application Load Balancer ARN. | | Service port \[service_port\] | The port on which the target is listening, if available. | | Object ID \[object_id\] | Possible values are: * Target ID * Target ID and target port, if available, in the following format: <target ID>#<target port>. For example: i-0123456789abcdef0#8080 {#data-discovered-aws-patterns__ul_z4s_sly_p2c} | | Comments \[comments\] | Comments related to the CI. | | Operational status \[operational_status\] | Operational status of the target. Possible values are Operational or Non-Operational. | | Install Status \[install_status\] | Installation status of the target. Possible values are Installed or Retired. | | Pool \[pool\] | References the Load Balancer Pool \[cmdb_ci_lb_pool\] table. | [Table 9. Load Balancer Pool Member \[cmdb_ci_lb_pool_member\]] {#data-discovered-aws-patterns__table_ntq_x3y_p2c} Note: By default, the Amazon AWS - LB Pool Member(LP) pattern doesn't execute discovery. To enable the discovery of AWS Application Load Balancer targets, set the sn_itom_pattern.discover_aws_app_pool_members MID Server property to true. For more information, see [Enable AWS Application Load Balancer target discovery](https://servicenow-prod.fluidtopics.net/58vzPc7L1zYB3awEzvbEBw "Enable the sn_itom_pattern.discover_aws_app_pool_members MID Server property to discover AWS Application Load Balancer targets."). Resources discovered using the Amazon AWS - Customer Gateway (LP) pattern : {#data-discovered-aws-patterns__table_rtm_ltw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name or ID if no Name is specified of the customer gateway. | | Object ID \[object_id\] | ID of the customer gateway. | | Connection Type \[connection_type\] | Type of VPN connection the customer gateway supports. | [Table 10. Customer Gateway \[cmdb_ci_customer_gateway\]] {#data-discovered-aws-patterns__table_rtm_ltw_mdc} {#data-discovered-aws-patterns__table_thc_mtw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name or ID if no Name is specified of the customer gateway. | | Object ID \[object_id\] | ID of the customer gateway. | [Table 11. Customer Gateway Endpoint \[cmdb_ci_endpoint_cust_gateway\]] {#data-discovered-aws-patterns__table_thc_mtw_mdc} Resources discovered using the Amazon AWS - discover Organization pattern : {#data-discovered-aws-patterns__table_sy5_b52_cbc__entry__2} | Field | Description | |-|-| | Name \[name\] | The unique identifier (ID) of the management account of an organization. | | Object ID \[object_id\] | The unique identifier (ID) of the management account of an organization. | | Root ID \[root_id\] | The unique identifier (ID) of an organization. | | Master Email \[master_email\] | The email address associated with the AWS account that is designated as the management account for the organization. | | Install Status \[install_status\] | The install status of the Organization based on the AvailablePolicyTypes status. | | Operational status \[operational_status\] | The operational status of the Organization based on the AvailablePolicyTypes status. | [Table 12. Cloud Organizations \[cmdb_ci_cloud_org\]] {#data-discovered-aws-patterns__table_sy5_b52_cbc} Resources discovered the using the Amazon AWS - Host (LP) pattern : {#data-discovered-aws-patterns__table_l3d_fb2_h4b__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of this host. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | CPU Core Count \[cpu_core_count\] | The number of host cores. | | State \[state\] | The current state of the host. | | Host Type \[host_type\] | The host type (instanceFamily). | | Cloud Vendor \[cloud_vendor\] | The cloud vendor: AWS. | | Virtual \[virtual\] | Virtual host: False. | [Table 13. Cloud Host \[cmdb_ci_cloud_host\]] {#data-discovered-aws-patterns__table_l3d_fb2_h4b} Resources discovered using the Amazon AWS - Internet Gateway (LP) pattern : {#data-discovered-aws-patterns__table_p3g_wfw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name or ID if no Name is specified for the internet gateway. | | Object ID \[object_id\] | ID of the internet gateway. | [Table 14. Internet Gateway \[cmdb_ci_internet_gateway\]] {#data-discovered-aws-patterns__table_p3g_wfw_lmb} {#data-discovered-aws-patterns__table_zsl_m5w_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name or ID if no Name is specified for the internet gateway. | | Object ID \[object_id\] | ID of the internet gateway. | [Table 15. Internet Gateway Endpoint \[cmdb_ci_endpoint_intgateway\]] {#data-discovered-aws-patterns__table_zsl_m5w_mdc} Resources discovered using the Amazon AWS - IP Address (LP) pattern : {#data-discovered-aws-patterns__table_qz4_zfw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or ID if no Name is specified for the Network Interface. | | IP Address \[ip_address\] | If available, the address of the Elastic IP address bound to the network interface. If not available, the Private IP. | | Object ID \[object_id\] | The ID of the Network Interface. | | Public DNS \[public_dns\] | The public DNS name if available. | | Private IP Address \[private_ip\] | The IPv4 address of the network interface within the subnet. | | Instance ID \[instance_id\] | The ID of the instance. | [Table 16. IP Address \[cmdb_ci_cloud_ip_address\]] {#data-discovered-aws-patterns__table_qz4_zfw_lmb} Resources discovered the using the Amazon AWS - Key Pair (LP) pattern : {#data-discovered-aws-patterns__table_ttg_dgw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the key pair. | | Object ID \[object_id\] | The ID of the key pair. | | Finger Print \[finger_print\] | If you used [CreateKeyPair](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateKeyPair.html) to create the key pair, this value is the SHA-1 digest of the DER encoded private key. If you used ImportKeyPair to provide AWS the public key, this value is the MD5 public key fingerprint as specified in section 4 of RFC 4716. | [Table 17. Cloud Key Pair \[cmdb_ci_cloud_key_pair\]] {#data-discovered-aws-patterns__table_ttg_dgw_lmb} Resources discovered using the Amazon AWS - LB Pool (LP) pattern : {#data-discovered-aws-patterns__table_ldm_ggw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the load balancer pool. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | Comments \[comments\] | Comments related to the CI. | [Table 18. Load Balancer Pool \[cmdb_ci_lb_pool\]] {#data-discovered-aws-patterns__table_ldm_ggw_lmb} Resources discovered using the Amazon AWS - LB Service (LP) pattern : {#data-discovered-aws-patterns__table_ums_3gw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the load balancer service. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | Port \[port\] | The port on which the load balancer is listening. | | Service Port \[service_port\] | The port on which the instance is listening. | | Server Protocol \[service_protocol\] | The protocol to use for routing traffic to instances: HTTP, HTTPS, TCP, or SSL. | | Listener Protocol \[service_protocol\] | The load balancer transport protocol to use for routing: HTTP, HTTPS, TCP, or SSL. | | Comments \[comments\] | Comments related to the CI. | [Table 19. Load Balancer Service \[cmdb_ci_lb_service\]] {#data-discovered-aws-patterns__table_ums_3gw_lmb} Resources discovered using the Amazon AWS - NAT Gateway (LP) pattern : {#data-discovered-aws-patterns__table_ohk_kgw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the NAT gateway. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | Install Status \[install_status\] | Provisioning status of the NAT gateway. | [Table 20. NAT Gateway \[cmdb_ci_nat_gateway\]] {#data-discovered-aws-patterns__table_ohk_kgw_lmb} {#data-discovered-aws-patterns__table_i32_lzw_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the NAT endpoint. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | [Table 21. NAT Endpoint \[cmdb_ci_endpoint_nat\]] {#data-discovered-aws-patterns__table_i32_lzw_mdc} Resources discovered using the Amazon AWS - Network (LP) pattern : {#data-discovered-aws-patterns__table_rt4_4gw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Virtual Private Cloud (VPC) network. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | State \[state\] | The current state of the VPC: pending or available. | | CIDR \[cidr\] | CIDR representation of the subnet. For example, 10.0.0.0/24. | | Install Status \[install_status\] | Resource provisioning status. | [Table 22. Cloud Network \[cmdb_ci_network\]] {#data-discovered-aws-patterns__table_rt4_4gw_lmb} Resources discovered using the Amazon AWS - NIC (LP) pattern : {#data-discovered-aws-patterns__table_wct_qgw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The Name or ID if no Name is specified for the Network Interface. | | Object ID \[object_id\] | The ID of the network interface. | | State \[state\] | The status of the network interface. The valid values are as follows: available, associated, attaching, in-use, or detaching. | | Private IP \[private_ip\] | The IPv4 address of the network interface within the subnet. | | IP Address \[ip_address\] | If available, the address of the Elastic IP address bound to the network interface. If not available, the Private IP. | | Public IP \[public_ip\] | The address of the Elastic IP address bound to the network interface. | [Table 23. Cloud Mgmt Network Interface \[cmdb_ci_nic\]] {#data-discovered-aws-patterns__table_wct_qgw_lmb} {#data-discovered-aws-patterns__table_aln_21x_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | IP address of the Load Balancer. | | Object ID \[object_id\] | If available, the address of the Elastic IP address bound to the network. If not available, the Private IP. | | IP Address \[ip_address\] | If available, the address of the Elastic IP address bound to the network interface. If not available, the Private IP. | | Comments \[comments\] | Comments related to the CI. | [Table 24. Cloud LB IPAddress \[cmdb_ci_cloud_lb_ipaddress\]] {#data-discovered-aws-patterns__table_aln_21x_mdc} {#data-discovered-aws-patterns__table_wdf_f1x_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the virtual network machine interface (VNIC) endpoint. | | Object ID \[object_id\] | Unique identifier, allocated by Amazon AWS Cloud for this resource. | | IP Address \[ip_address\] | If available, the address of the Elastic IP address bound to the network interface. If not available, the Private IP. | | Host \[host\] | The ID of the instance. | [Table 25. VNIC Endpoint \[cmdb_ci_endpoint_vnic\]] {#data-discovered-aws-patterns__table_wdf_f1x_mdc} Resources discovered using the Amazon AWS - Organizational Units (LP) pattern : {#data-discovered-aws-patterns__table_b4d_kx2_cbc__entry__2} | Field | Description | |-|-| | Name \[name\] | The user-friendly name of the Organizational Unit (OU). | | Object ID \[object_id\] | The unique identifier (ID) associated with this OU. The ID is unique to the organization. | | Organizational ID \[aws_org_id\] | The unique identifier (ID) associated with this OU. The ID is unique to the organization. | | Org Unit Parent ID \[org_unit_parent_id\] | The ID of the root or the immediate parent OU. | [Table 26. AWS Organizational Unit \[cmdb_ci_aws_org_unit\]] {#data-discovered-aws-patterns__table_b4d_kx2_cbc} Resources discovered using the Amazon AWS - Public IP Address (LP) pattern : {#data-discovered-aws-patterns__table_dbn_4hw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or allocation ID, if no name is specified for the public IP address. | | Object ID \[object_id\] | The ID representing the allocation of the address for the use with EC2-VPC. | | Public ID Address \[public_ip\] | The elastic IP address. | [Table 27. Cloud Public IP Address \[cmdb_ci_cloud_public_ipaddress\]] {#data-discovered-aws-patterns__table_dbn_4hw_lmb} Resources discovered using the Amazon AWS - Route Table (LP) pattern : {#data-discovered-aws-patterns__table_uqv_rhw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The ID of the route table. | | State \[state\] | If the route table is discoverable, the value is available. | | Object ID \[object_id\] | The name or ID, if no name is specified for the route table. | [Table 28. Route Table \[cmdb_ci_route_table\]] {#data-discovered-aws-patterns__table_uqv_rhw_lmb} {#data-discovered-aws-patterns__table_gnx_fbx_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or ID, if no name is specified for the route table. | | Object ID \[object_id\] | The ID of the route table. | [Table 29. Route Table Endpoint \[cmdb_ci_endpoint_route_table\]] {#data-discovered-aws-patterns__table_gnx_fbx_mdc} Resources discovered using the Amazon AWS - Security Group (LP) pattern : {#data-discovered-aws-patterns__table_ws5_vhw_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the security group. | | Object ID \[object_id\] | The ID of the security group. | [Table 30. Compute Security Group \[cmdb_ci_compute_security_group\]] {#data-discovered-aws-patterns__table_ws5_vhw_lmb} Resources discovered using the Amazon AWS - SSM Cloud Agents (LP) pattern : The Amazon AWS - SSM Cloud Agents (LP) pattern introduces the following CI class that extends an existing CMDB class. {#data-discovered-aws-patterns__table_extends_ssm__entry__2} | CI class | Extends from | |-|-| | Cloud System Management Agent \[cmdb_ci_cloud_system_management_agent\] | Virtual Machine Object \[cmdb_ci_vm_object\] | [Table 31. CI class introduced by this pattern] {#data-discovered-aws-patterns__table_extends_ssm} {#data-discovered-aws-patterns__table_dnd_xpy_1fc__entry__2} | Field | Description | |-|-| | Cloud Agent Type \[cloud_agent_type\] | Type of cloud agent: AWS SSM. | | Install Status \[install_status\] | Install status of the AWS Systems Manager (SSM) agent: * Installed: The agent is currently running. * Absent: The agent is not currently running. {#data-discovered-aws-patterns__ul_rlw_x2n_cfc} | | IP Address \[ip_address\] | Address of the VM instance. | | Name \[name\] | Name of the VM instance that the SSM agent is running on. | | Object ID \[object_id\] | ID of the VM instance. | | Operational status \[operational_status\] | Operational status of the agent service. Possible values are Operational or Non-Operational. | | Operating System Platform \[operating_system_platform\] | Operating system type of the VM instance. | | Resource Type \[resource_type\] | Type of resource managed by SSM. Possible values are EC2Instance or ManagedInstance. | | Version \[version\] | Version of the SSM agent. | [Table 32. Cloud System Management Agent \[cmdb_ci_cloud_system_management_agent\]] {#data-discovered-aws-patterns__table_dnd_xpy_1fc} Resources discovered using the Amazon AWS - Storage (LP) pattern : {#data-discovered-aws-patterns__table_o5f_13w_lmb__entry__2} | Field | Description | |-|-| | State \[state\] | The volume state. The following values are valid: creating, available, in-use, deleting, deleted, or error. | | Storage Type \[storage_type\] | For example, hard-coded value: block. | | Volume ID \[volume_id\] | The volume type. For example, gp2 for General Purpose SSD, io1 for Provisioned IOPS SSD, st1 for Throughput Optimized HDD, sc1 for Cold HDD, or standard for Magnetic volumes. | | Name \[name\] | The name or ID, if no name is specified for the volume. | | Size Bytes \[size_bytes\] | The size of the volume, in bytes. | | Object ID \[object_id\] | The ID of the volume. | [Table 33. Storage Volume \[cmdb_ci_storage_volume\]] {#data-discovered-aws-patterns__table_o5f_13w_lmb} {#data-discovered-aws-patterns__table_gh5_tbx_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or ID, if no name is specified for the volume. | | Object ID \[object_id\] | The ID of the volume. | [Table 34. Block Endpoint \[cmdb_ci_endpoint_block\]] {#data-discovered-aws-patterns__table_gh5_tbx_mdc} Resources discovered using the Amazon AWS - Sub Account (LP) pattern : {#data-discovered-aws-patterns__table_ppq_c3w_lmb__entry__2} | Field | Description | |-|-| | Account ID \[account_id\] | Unique identifier (ID) of the account. | | Object ID \[object_id\] | Unique identifier (ID) of the account. | | Datacenter Type \[datacenter_type\] | Hard-coded value: cmdb_ci_aws_datacenter. | | Name \[name\] | User-friendly name of the account. | | Is Master Account \[is_master_account\] | Boolean attribute indicating if this account is the management account or not. | | Account Email \[account_email\] | Email address of the AWS service account. | [Table 35. Cloud Service Account \[cmdb_ci_cloud_service_account\]] {#data-discovered-aws-patterns__table_ppq_c3w_lmb} Resources discovered using the Amazon AWS - Subnet (LP) pattern : {#data-discovered-aws-patterns__table_pjl_h3w_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or ID, if no name is specified for the subnet. | | Object ID \[object_id\] | The ID of the subnet. | | CIDR \[cidr\] | The IPv4 CIDR block assigned to the subnet. | | Available IP Count \[available_ip_count\] | The number of unused private IPv4 addresses in the subnet. The IPv4 addresses for any stopped instances are considered unavailable. | | State \[state\] | The current state of the subnet. The following values are valid: pending or available. | [Table 36. Cloud Subnet \[cmdb_ci_cloud_subnet\]] {#data-discovered-aws-patterns__table_pjl_h3w_lmb} Resources discovered using the Amazon AWS - VPN Connections (LP) pattern : {#data-discovered-aws-patterns__table_lkb_m3w_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the project that is used for the discovery. | | Object ID \[object_id\] | The name or ID, if no name is specified for the VPN connection. | | State \[state\] | The current state of the VPN connection. The following values are valid: pending, available, deleting, or deleted. | [Table 37. VPN Connection \[cmdb_ci_vpn_connection\]] {#data-discovered-aws-patterns__table_lkb_m3w_lmb} Resources discovered using the Amazon AWS - VPN Gateway (LP) pattern : {#data-discovered-aws-patterns__table_mcw_43w_lmb__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or ID, if no name is specified for the VPN Gateway. | | Object ID \[object_id\] | The ID of the virtual private gateway. | | Connection Type \[connection_type\] | The type of VPN connection the virtual private gateway supports. | [Table 38. Virtual Private Gateway \[cmdb_ci_virtual_pvt_gateway\]] {#data-discovered-aws-patterns__table_mcw_43w_lmb} {#data-discovered-aws-patterns__table_cmq_ldx_mdc__entry__2} | Field | Description | |-|-| | Name \[name\] | The name or ID, if no name is specified for the VPN Gateway. | | Object ID \[object_id\] | The ID of the virtual private gateway. | | Connection Type \[connection_type\] | The type of VPN connection the virtual private gateway supports. | [Table 39. Virtual Private Gateway Endpoint \[cmdb_ci_endpoint_vpg\]] {#data-discovered-aws-patterns__table_cmq_ldx_mdc} Resources discovered using the Amazon AWS - Web ACL (LP) pattern : The Amazon AWS - Web ACL (LP) pattern introduces the following CI class that extends an existing CMDB class. {#data-discovered-aws-patterns__table_extends_webacl__entry__2} | CI class | Extends from | |-|-| | Web ACL \[cmdb_ci_web_acl\] | Virtual Machine Object \[cmdb_ci_vm_object\] | [Table 40. CI class introduced by this pattern] {#data-discovered-aws-patterns__table_extends_webacl} {#data-discovered-aws-patterns__table_il1_nbb_y2c__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the web access control list (web ACL). | | Object ID \[object_id\] | Unique ID for the web ACL from AWS. | | Default Action \[defaul_action\] | Default action when no rules in the web ACL match. Possible values are Allow or Deny. | | Description \[short_description\] | Description of web ACL provided by AWS. | | Operational status \[operational_status\] | Whether the web ACL is enabled or disabled. Possible values are Operational or Retired. | [Table 41. Web ACL \[cmdb_ci_web_acl\]] {#data-discovered-aws-patterns__table_il1_nbb_y2c} Note: Security Operations users can leverage the integration with Discovery to import web ACL rules and load balancers with attached web ACLs. For more information on setting ACL rules and using the Mitigation Controls Monitoring app, see [Configure the AWS WAF integration for mitigation controls monitoring](https://www.servicenow.com/docs/access?context=spc-install-config-aws-waf&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US). ## Events discovered by Discovery during horizontal discovery {#data-discovered-aws-patterns__section_glt_jsd_mmb} Discovery uses patterns to find events created for Amazon AWS Cloud components. If there are events that indicate the change of state in one of the Amazon AWS Cloud components, it triggers discovery of Amazon AWS Cloud components using the patterns. {#data-discovered-aws-patterns__table_fmp_4td_mmb__entry__2} | Pattern | CI | |-|-| | Amazon AWS Virtual Server Events | Virtual Machine Instance \[cmdb_ci_vm_instance\] | | Amazon AWS Security Group Events | Compute Security Group \[cmdb_ci_compute_security_group\] | | Amazon AWS Subnet Events | Cloud Subnet \[cmdb_ci_cloud_subnet\] | | Amazon AWS Storage Events | Storage Volume \[cmdb_ci_storage_volume\] | | Amazon AWS Network Events | Cloud Network \[cmdb_ci_network\] | | Amazon AWS Classic LB Events | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | | Amazon AWS Application and Network LBs Events | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | [Table 42. Patterns used for event discovery] {#data-discovered-aws-patterns__table_fmp_4td_mmb} Figure 2. Dependency Views displaying the cloud load balancer and connected components Figure 3. Dependency Views displaying components connected to the cloud network in the AWS environment Figure 4. Dependency Views showing Virtual Machine and connected components in the AWS environment ## CI relationships {#data-discovered-aws-patterns__section_prw_ffm89wj} The AWS patterns create the following relationships and references to support AWS discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. Relationships discovered using the Amazon AWS - Availability Zone (LP) pattern : {#data-discovered-aws-patterns__table_wy5_hlp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | AWS Datacenter \[cmdb_ci_aws_datacenter\] | Contains::Contained by | Availability Zone \[cmdb_ci_availability_zone\] | [Table 43. CI relationships] {#data-discovered-aws-patterns__table_wy5_hlp_4mb} Relationships discovered using the Amazon AWS - Classic LB (LP) pattern : {#data-discovered-aws-patterns__table_xkw_hlp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Load Balancer Service \[cmdb_ci_lb_service\] | Hosted on::Hosts | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | | 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\] | | Load Balancer Pool \[cmdb_ci_lb_pool\] | Hosted on::Hosts | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | | Load Balancer Pool \[cmdb_ci_lb_pool\] | Owns::Owned by | Load Balancer Pool Member \[cmdb_ci_lb_pool_member\] | | 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\] | Owns::Owned by | Cloud LB IPAddress \[cmdb_ci_cloud_lb_ipaddress\] | | 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 | Compute Security Group \[cmdb_ci_compute_security_group\] | [Table 44. CI relationships] {#data-discovered-aws-patterns__table_xkw_hlp_4mb} Relationships discovered using the Amazon AWS - LB Pool Member(LP) pattern : {#data-discovered-aws-patterns__table_s23_s3y_p2c__entry__3} | CI | Relationship | CI | |-|-|-| | Load Balancer Pool \[cmdb_ci_lb_pool\] | Owns::Owned by | Load Balancer Pool Member \[cmdb_ci_lb_pool_member\] | [Table 45. CI relationships] {#data-discovered-aws-patterns__table_s23_s3y_p2c} {#data-discovered-aws-patterns__table_ci_references_lbpm__entry__3} | CI | Field | Referenced CI | |-|-|-| | Load Balancer Pool Member \[cmdb_ci_lb_pool_member\] | Pool \[pool\] | Load Balancer Pool \[cmdb_ci_lb_pool\] | [Table 46. CI references] {#data-discovered-aws-patterns__table_ci_references_lbpm} Note: By default, the Amazon AWS - LB Pool Member(LP) pattern doesn't execute discovery. To enable the discovery of AWS Application Load Balancer targets, set the sn_itom_pattern.discover_aws_app_pool_members MID Server property to true. For more information, see [Enable AWS Application Load Balancer target discovery](https://servicenow-prod.fluidtopics.net/58vzPc7L1zYB3awEzvbEBw "Enable the sn_itom_pattern.discover_aws_app_pool_members MID Server property to discover AWS Application Load Balancer targets."). Relationships discovered using the Amazon AWS - Customer Gateway (LP) pattern : {#data-discovered-aws-patterns__table_fjx_hlp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Customer Gateway \[cmdb_ci_customer_gateway\] | Hosted on::Hosts | Virtual Machine Instance \[cmdb_ci_instance\] | | Customer Gateway \[cmdb_ci_customer_gateway\] | Implement End Point To::Implement End Point From | Customer Gateway \[cmdb_ci_endpoint_cust_gateway\] | [Table 47. CI relationships] {#data-discovered-aws-patterns__table_fjx_hlp_4mb} Relationships discovered using the Amazon AWS - Host (LP) pattern : {#data-discovered-aws-patterns__table_emq_cf2_h4b__entry__3} | CI | Relationship | CI | |-|-|-| | Host \[cmdb_ci_cloud_host\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | Virtual Machine Instance \[cmdb_ci_vm_instance\] | Runs on::Runs | Host \[cmdb_ci_cloud_host\] | [Table 48. CI relationships] {#data-discovered-aws-patterns__table_emq_cf2_h4b} Relationships discovered using the Amazon AWS - Internet Gateway (LP) pattern : {#data-discovered-aws-patterns__table_f4w_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Internet Gateway \[cmdb_ci_internet_gateway\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | Internet Gateway \[cmdb_ci_internet_gateway\] | Implement End Point To::Implement End Point From | Internet Gateway EP \[cmdb_ci_endpoint_intgateway\] | | Cloud Network \[cmdb_ci_network\] | Use End Point To::Use End Point From | Internet Gateway EP \[cmdb_ci_endpoint_intgateway\] | [Table 49. CI relationships] {#data-discovered-aws-patterns__table_f4w_zqp_4mb} Relationships discovered using the Amazon AWS - IP Address (LP) pattern : {#data-discovered-aws-patterns__table_i5w_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Key Pair \[cmdb_ci_cloud_key_pair\] | Contains::Contained by | IP Address \[cmdb_ci_cloud_ip_address\] | [Table 50. CI relationships] {#data-discovered-aws-patterns__table_i5w_zqp_4mb} Relationships discovered using the Amazon AWS - Key Pair (LP) pattern : {#data-discovered-aws-patterns__table_mcx_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Servers \[cmdb_ci_server\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 51. CI relationships] {#data-discovered-aws-patterns__table_mcx_zqp_4mb} Relationships discovered using the Amazon AWS - LB Pool (LP) pattern : {#data-discovered-aws-patterns__table_nkx_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Load Balancer Pool \[cmdb_ci_lb_pool\] | Hosted on::Hosts | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | [Table 52. CI relationships] {#data-discovered-aws-patterns__table_nkx_zqp_4mb} Relationships discovered using the Amazon AWS - LB Service (LP) pattern : {#data-discovered-aws-patterns__table_trr_wsp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Load Balancer Service \[cmdb_ci_lb_service\] | Hosted on::Hosts | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | [Table 53. CI relationships] {#data-discovered-aws-patterns__table_trr_wsp_4mb} Relationships discovered using the Amazon AWS - NAT Gateway (LP) pattern : {#data-discovered-aws-patterns__table_etx_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | NAT Gateway \[cmdb_ci_nat_gateway\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | NAT Gateway \[cmdb_ci_nat_gateway\] | Implement End Point To::Implement End Point From | NAT EP \[cmdb_ci_endpoint_nat\] | | Network \[cmdb_ci_network\] | Use End Point To::Use End Point From | NAT EP \[cmdb_ci_endpoint_nat\] | [Table 54. CI relationships] {#data-discovered-aws-patterns__table_etx_zqp_4mb} Relationships discovered using the Amazon AWS - Network (LP) pattern : {#data-discovered-aws-patterns__table_tcy_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Network \[cmdb_ci_network\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 55. CI relationships] {#data-discovered-aws-patterns__table_tcy_zqp_4mb} Relationships discovered using the Amazon AWS - NIC (LP) pattern : {#data-discovered-aws-patterns__table_ymy_zqp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Owns::Owned by | Cloud LB IPAddress \[cmdb_ci_cloud_lb_ipaddress\] | | Virtual Machine Instance \[cmdb_ci_vm_instance\] | Use End Point To::Use End Point From | VNIC Endpoint \[cmdb_ci_endpoint_vnic\] | | Cloud Subnet \[cmdb_ci_cloud_subnet\] | Contains::Contained by | NIC \[cmdb_ci_nic\] | | VNIC Endpoint \[cmdb_ci_endpoint_vnic\] | Implement End Point To::Implement End Point From | NIC \[cmdb_ci_nic\] | | NIC \[cmdb_ci_nic\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 56. CI relationships] {#data-discovered-aws-patterns__table_ymy_zqp_4mb} Relationships discovered using the Amazon AWS - Organizational Units (LP) pattern : {#data-discovered-aws-patterns__table_ytd_kbf_cbc__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Organization \[cmdb_ci_cloud_org\] | Contains::Contained by | AWS Organizational Unit \[cmdb_ci_aws_org_unit\] | | AWS Organizational Unit \[cmdb_ci_aws_org_unit\] | Contains::Contained by | Cloud Service Account \[cmdb_ci_cloud_service_account\] | [Table 57. CI relationships] {#data-discovered-aws-patterns__table_ytd_kbf_cbc} {#data-discovered-aws-patterns__table_ci_references_org__entry__3} | CI | Field | Referenced CI | |-|-|-| | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | AWS Organizational Unit \[cmdb_ci_aws_org_unit\] | [Table 58. CI references] {#data-discovered-aws-patterns__table_ci_references_org} Relationships discovered using the Amazon AWS - Public IP Address (LP) pattern : {#data-discovered-aws-patterns__table_dmd_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Public IP Address \[cmdb_ci_cloud_public_ipaddress\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 59. CI relationships] {#data-discovered-aws-patterns__table_dmd_gyp_4mb} Relationships discovered using the Amazon AWS - Route Table (LP) pattern : {#data-discovered-aws-patterns__table_dm2_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Network \[cmdb_ci_network\] | Contains::Contained by | Route Table \[cmdb_ci_route_table\] | | Cloud Subnet \[cmdb_ci_cloud_subnet\] | Use End Point To::Use End Point From | Route Table Endpoint \[cmdb_ci_endpoint_route_table\] | | Route Table \[cmdb_ci_route_table\] | Implement End Point To::Implement End Point From | Route Table Endpoint \[cmdb_ci_endpoint_route_table\] | [Table 60. CI relationships] {#data-discovered-aws-patterns__table_dm2_gyp_4mb} Relationships discovered using the Amazon AWS - Security Group (LP) pattern : {#data-discovered-aws-patterns__table_nw2_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Network \[cmdb_ci_network\] | Contains::Contained by | Compute Security Group \[cmdb_ci_compute_security_group\] | | Compute Security Group \[cmdb_ci_compute_security_group\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 61. CI relationships] {#data-discovered-aws-patterns__table_nw2_gyp_4mb} Relationships discovered using the Amazon AWS - SSM Cloud Agents (LP) pattern : {#data-discovered-aws-patterns__table_ky5_2xx_bfc__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud System Management Agent \[cmdb_ci_cloud_system_management_agent\] | Runs on::Runs | Virtual Machine Instance \[cmdb_ci_vm_instance\] | [Table 62. CI relationships] {#data-discovered-aws-patterns__table_ky5_2xx_bfc} Relationships discovered using the Amazon AWS - Storage (LP) pattern : {#data-discovered-aws-patterns__table_yff_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Virtual Machine Instance \[cmdb_ci_instance\] | Use End Point To::Use End Point From | Block Endpoint \[cmdb_ci_endpoint_block\] | | Block Endpoint \[cmdb_ci_endpoint_block\] | Implement End Point To::Implement End Point From | Storage Volume \[cmdb_ci_storage_volume\] | | Availability Zone \[cmdb_ci_availability_zone\] | Contains::Contained by | Storage Volume \[cmdb_ci_storage_volume\] | | Storage Volume \[cmdb_ci_storage_volume\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 63. CI relationships] {#data-discovered-aws-patterns__table_yff_gyp_4mb} Relationships discovered using the Amazon AWS - Subnet (LP) pattern : {#data-discovered-aws-patterns__table_gpf_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Network \[cmdb_ci_network\] | Contains::Contained by | Cloud Subnet \[cmdb_ci_cloud_subnet\] | | Availability Zone \[cmdb_ci_availability_zone\] | Contains::Contained by | Cloud Subnet \[cmdb_ci_cloud_subnet\] | [Table 64. CI relationships] {#data-discovered-aws-patterns__table_gpf_gyp_4mb} Relationships discovered using the Amazon AWS - VPN Connections (LP) pattern : {#data-discovered-aws-patterns__table_dkg_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Customer Gateway \[cmdb_ci_customer_gateway\] | Contains::Contained by | VPN Connection \[cmdb_ci_vpn_connection\] | | Virtual Private Gateway \[cmdb_ci_virtual_pvt_gateway\] | Contains::Contained by | VPN Connection \[cmdb_ci_vpn_connection\] | | VPN Connection \[cmdb_ci_vpn_connection\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 65. CI relationships] {#data-discovered-aws-patterns__table_dkg_gyp_4mb} Relationships discovered using the Amazon AWS - VPN Gateway (LP) pattern : {#data-discovered-aws-patterns__table_twg_gyp_4mb__entry__3} | CI | Relationship | CI | |-|-|-| | Virtual Private Gateway \[cmdb_ci_virtual_pvt_gateway\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | Virtual Private Gateway \[cmdb_ci_virtual_pvt_gateway\] | Implement End Point To::Implement End Point From | Virtual Private Gateway Endpoint \[cmdb_ci_endpoint_vpg\] | | Network \[cmdb_ci_network\] | Use End Point To::Use End Point From | Virtual Private Gateway Endpoint \[cmdb_ci_endpoint_vpg\] | [Table 66. CI relationships] {#data-discovered-aws-patterns__table_twg_gyp_4mb} Relationships discovered using the Amazon AWS - Web ACL (LP) pattern : {#data-discovered-aws-patterns__table_acx_bdb_y2c__entry__3} | CI | Relationship | CI | |-|-|-| | Web ACL \[cmdb_ci_web_acl\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 67. CI relationships] {#data-discovered-aws-patterns__table_acx_bdb_y2c} Note: Security Operations users can leverage the integration with Discovery to import web ACL rules and load balancers with attached web ACLs. For more information on setting ACL rules and using the Mitigation Controls Monitoring app, see [Configure the AWS WAF integration for mitigation controls monitoring](https://www.servicenow.com/docs/access?context=spc-install-config-aws-waf&version=yokohama&pubname=yokohama-security-management&ft:locale=en-US). ## Services discovered by patterns {#data-discovered-aws-patterns__section_kjs_st1_qmb} Horizontal discovery finds EC2 and VPC services running on AWS resources.{#data-discovered-aws-patterns__table_n1n_yt1_qmb__entry__3} | Service name | CI class | Pattern | |-|-|-| | AWS::EC2::SecurityGroup | Compute Security Group \[cmdb_ci_compute_security_group\] | Amazon AWS Security Group Events | | AWS::EC2::Subnet | Cloud Subnet \[cmdb_ci_cloud_subnet\] | Amazon AWS Subnet Events | | AWS::EC2::VPC | Cloud Network \[cmdb_ci_network\] | Amazon AWS Network Events | | AWS::EC2::Instance | Virtual Machine Instance \[cmdb_ci_vm_instance\] | Amazon AWS Virtual Server Events | | EQS::EC2::Volume | Storage Volume \[cmdb_ci_storage_volume\] | Amazon AWS Elastic Block Storage | | AWS::ElasticLoadBalancingV2::LoadBalancer | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Amazon AWS Application and Network LBs Events | | AWS::ElasticLoadBalancing::LoadBalancer | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] | Amazon AWS Classic LBs Events | [Table 68. Services discovered by Discovery using patterns] {#data-discovered-aws-patterns__table_n1n_yt1_qmb} ## Data collected by Service Mapping during tag-based discovery {#data-discovered-aws-patterns__section_kmf_r3y_qpb} Service Mapping uses tag-based discovery to create service instance maps including the Cloud components. The Service Mapping application comes with the following preconfigured CI relationships used for tag-based discovery. These CI relationships are available from the 1.0.68 release on the ServiceNow Store. {#data-discovered-aws-patterns__id_yqp_xhy_qpb__entry__3} | CI | Relationship | CI | |-|-|-| | Configuration Item \[cmdb_ci\] | Hosted on::Hosts | Logical Datacenter \[cmdb_ci_logical_datacenter\] | | Logical Datacenter \[cmdb_ci_logical_datacenter\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] | [ ] {#data-discovered-aws-patterns__id_yqp_xhy_qpb} * **[Limit AWS discovery to datacenters with resources](https://servicenow-prod.fluidtopics.net/7X~3RQ4Yjaoi5xw8DAdmTA)** Optimize AWS discovery by limiting it to datacenters with resources. **Related concepts** * [Kubernetes discovery using patterns](https://servicenow-prod.fluidtopics.net/Nq0fHYmeSm4QYmSRUrjWJA "The ServiceNow ITOM Visibility finds Kubernetes and OpenShift components using patterns and creates application services containing them. Discovery also finds Kubernetes events and frequently updates the CMDB to reflect the dynamic Kubernetes environment.") **Related reference** * [AWS Certificate Manager discovery](https://servicenow-prod.fluidtopics.net/YHHSwOGkLkB~fQOqEn7_Rw "Cloud Discovery uses Patterns to discover certificate data that the Amazon AWS Cloud Certificate Manager (ACM) manages. Discovering this data requires installing and updating Discovery and Service Mapping Patterns and Certificate Inventory and Management.") * [Amazon Bedrock pattern-based discovery](https://servicenow-prod.fluidtopics.net/5y6IYvI2tBfMu5S2dAy~Ug "AI Agent Topology Mapping discovers Amazon Bedrock AI services, agents, and models during horizontal discovery.")