---
sourceDocument: Zurich IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Data collected for AWS

# Data collected for Amazon AWS
Cloud Discovery {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Data collected for Amazon AWS Cloud Discovery

Amazon AWS Cloud Discovery in ServiceNow collects detailed information about cloud resources within AWS datacenters to support configuration management and visibility.
To utilize this capability effectively, customers should ensure they have the latest versions of the Discovery and Service Mapping Patterns applications from the ServiceNow Store, as updated patterns are released quarterly to enhance data collection.
Show full answer Show less  

## Prerequisites and Setup

* Verify that the following applications are up to date: Discovery and Service Mapping Patterns, CMDB CI Class Models, and Visibility Content.
* Create and configure a discovery schedule using the Cloud Discovery Workspace.
* Verify REST API permissions by downloading the Cloud Discovery patterns spreadsheet, which details required user permissions, pattern names, CI Classes, and vendor documentation links.
* Test AWS REST APIs using tools like Postman to ensure connectivity and permissions.

## Key Data Collected

ServiceNow Discovery collects and maps various AWS cloud resources into specific CMDB tables, enabling customers to maintain accurate and comprehensive asset records:

* **AWS Datacenter:** Basic location data including region and object ID.
* **Availability Zones:** Zones within AWS regions.
* **Virtual Machine Instances:** Details such as name, state, CPUs, memory, disks, and network adapters.
* **Compute Security Groups:** Security group names, states, and object IDs.
* **Images and Hardware Types:** Image properties (OS, root device, source) and hardware specs (vCPUs, memory, storage).
* **Storage Volumes:** Storage type, size, state, and identifiers.
* **Cloud Networks and Subnets:** Network names, states, CIDR blocks, and subnet statuses.
* **Management Network Interfaces:** NIC details including MAC manufacturer and status.
* **Load Balancers and Resource Groups:** Names, states, and unique IDs.
* **Public IP Addresses and Storage Accounts:** IP details, DNS, SKU names, and states.
* **DNS Aliases and Names:** DNS records with categories, statuses, and IP addresses.
* **Cloud Databases:** Database name, type, domain name, state, TCP ports, instance class, and backup settings.
* **Cloud Web Servers:** Server names, install status, vendor, FQDN, and operational status.
* **Kubernetes Clusters:** Cluster identifiers, ports, vendor info, and fully qualified domain names.

## Practical Benefits for ServiceNow Customers

By leveraging AWS Cloud Discovery, customers gain visibility into their AWS infrastructure within the ServiceNow CMDB, facilitating better asset management, compliance monitoring, and operational insight. The structured data supports automation, service mapping, and integration with other ITSM processes.

Regular updates to discovery patterns ensure coverage of new AWS resources and features, helping maintain an accurate and current configuration database aligned with evolving cloud environments.  
Discovery collects information about cloud resources in AWS datacenters. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Request apps on the Store {#cloud-disco-aws-data-collected__section_y3k_3pl_rlb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website 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).{#cloud-disco-aws-data-collected__inline-send-to-store}

## Prerequisites {#cloud-disco-aws-data-collected__section_asl_pcm_jzb}

Verify that the applications are up to date.
:
    * Discovery and Service Mapping Patterns.
    * CMDB CI Class Models.
    * Visibility Content.
    {#cloud-disco-aws-data-collected__ul_aln_qlb_5yb}

Configure a discovery schedule
:   [Create a discovery schedule in Cloud Discovery Workspace](https://www.servicenow.com/docs/HqOgLUuXYs~qteHC5QcuyA "Create schedules for discovering cloud resources based on the discovery method that you choose: service accounts or IP ranges. The discovery schedule defines the various settings for the cloud discovery.")

## Verify the REST API Permissions {#cloud-disco-aws-data-collected__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.{#cloud-disco-aws-data-collected__cloud-discovery-api-paragraph}
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 for AWS Cloud Discovery {#cloud-disco-aws-data-collected__section_ivt_pbv_nz}

The following tables show examples of data collected during AWS Cloud Discovery.  
{#cloud-disco-aws-data-collected__table_hsy_ql3_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Region | region |
| Object ID | object_id |
[Table 1. AWS Datacenter \[cmdb_ci_aws_datacenter\]]

{#cloud-disco-aws-data-collected__table_hsy_ql3_cy}  
{#cloud-disco-aws-data-collected__table_jmt_rtv_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
[Table 2. Availability Zone \[cmdb_ci_availability_zone\]]

{#cloud-disco-aws-data-collected__table_jmt_rtv_cy}  
{#cloud-disco-aws-data-collected__table_igv_rtv_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| State | state |
| Object ID | object_id |
| CPUs | cpus |
| Disks | disks |
| Memory | memory |
| Network adapters | nics |
| VM Instance ID | vm_inst_id |
[Table 3. Virtual Machine Instance \[cmdb_ci_vm_instance\]]

{#cloud-disco-aws-data-collected__table_igv_rtv_cy}  
{#cloud-disco-aws-data-collected__table_csk_4cv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| State | state |
[Table 4. Compute Security Groups \[cmdb_ci_compute_security_group\]]

{#cloud-disco-aws-data-collected__table_csk_4cv_nz}  
{#cloud-disco-aws-data-collected__table_j1k_pcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Guest OS | guest_os |
| Root device type | root_device_type |
| Image source | image_source |
| Image type | image_type |
[Table 5. Images \[cmdb_ci_os_template\]]

{#cloud-disco-aws-data-collected__table_j1k_pcv_nz}  
{#cloud-disco-aws-data-collected__table_tpd_qcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| vCPUs | vcpus |
| Memory MB | memory_mb |
| Local Storage GB | local_storage_gb |
[Table 6. Hardware Type \[cmdb_ci_compute_template\]]

{#cloud-disco-aws-data-collected__table_tpd_qcv_nz}  
{#cloud-disco-aws-data-collected__table_ggz_qcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| State | state |
| Object ID | object_id |
| Storage type | storage_type |
| Size | size |
[Table 7. Storage Volume \[cmdb_ci_storage_volume\]]

{#cloud-disco-aws-data-collected__table_ggz_qcv_nz}  
{#cloud-disco-aws-data-collected__table_xgb_scv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| State\* | state |
| CIDR\* | cidr |
[Table 8. Cloud Networks \[cmdb_ci_network\] and VMware vCenter Network \[cmdb_ci_vcenter_network\]]

{#cloud-disco-aws-data-collected__table_xgb_scv_nz}\*Not found on VMware vCenter networks.  
{#cloud-disco-aws-data-collected__table_v4h_jfv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Status | status |
| CIDR | cidr |
[Table 9. Cloud Subnets \[cmdb_ci_cloud_subnet\]]

{#cloud-disco-aws-data-collected__table_v4h_jfv_nz}  
{#cloud-disco-aws-data-collected__table_ebc_tcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Netmask | netmask |
| MAC Manufacturer | mac_manufacturer |
| Status | install_status |
[Table 10. Cloud Management Network Interfaces \[cmdb_ci_nic\]]

{#cloud-disco-aws-data-collected__table_ebc_tcv_nz}  
{#cloud-disco-aws-data-collected__table_csh_5cv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| State | state |
[Table 11. Cloud Load Balancers \[cmdb_ci_cloud_load_balancer\]]

{#cloud-disco-aws-data-collected__table_csh_5cv_nz}  
{#cloud-disco-aws-data-collected__table_hwb_zcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| State | state |
[Table 12. Resource Groups \[cmdb_ci_resource_group\]]

{#cloud-disco-aws-data-collected__table_hwb_zcv_nz}  
{#cloud-disco-aws-data-collected__table_ljd_1dv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Public IP address | public_ip_address |
| Public DNS | public_dns |
[Table 13. Public IP Addresses \[cmdb_ci_cloud_public_ipaddress\]]

{#cloud-disco-aws-data-collected__table_ljd_1dv_nz}  
{#cloud-disco-aws-data-collected__table_k4b_wmb_qz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Sku Name | sku_name |
| State | state |
[Table 14. Storage Accounts \[cmdb_ci_cloud_storage_account\]]

{#cloud-disco-aws-data-collected__table_k4b_wmb_qz}  
{#cloud-disco-aws-data-collected__table_ymc_vzp_cdb__entry__2}

| Label | Field name |
|-|-|
| DNS Alias \[cmdb_ci_dns_alias\] ||
| Name | name |
| Category | category |
| Status | status |
| DNS name \[cmdb_ci_dns_name\] ||
| Name | name |
| IP address | ip_address |
[Table 15. DNS Alias \[cmdb_ci_dns_alias\] and DNS name \[cmdb_ci_dns_name\]]

{#cloud-disco-aws-data-collected__table_ymc_vzp_cdb}  
{#cloud-disco-aws-data-collected__table_wbh_q4s_mbb__entry__3}

| Label | Field Name | Description |
|-|-|-|
| Name | name | The name of the database that you created in AWS. |
| Object ID | object_id | This is also the name of the database. |
| Type | Type | The type of database you created. |
| Fully qualified domain name | fqdn | The FQDN that AWS assigned to your database. An example format for AWS is as follows: `database-name.{random-number}.{datacenter}.rds.amazonaws.com` |
| State | state | The state of the database: whether it is Available or Terminated. |
| TCP port(s) | tcp_port | The TCP port that the database communicates through. |
| Category | category | The instance class of the database, for example: db.t2.micro. |
| Automated Backups | automated_backup | Indicates whether automated backups are enabled and the retention period. |
[Table 16. Cloud DataBases \[cmdb_ci_cloud_database\]]

{#cloud-disco-aws-data-collected__table_wbh_q4s_mbb}  
{#cloud-disco-aws-data-collected__table_ar5_2gd_4db__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Install status | install_status |
| Vendor | vendor |
| Fully qualified domain name | fqdn |
| Operational status | operational_status |
| State | state |
[Table 17. Cloud WebServer \[cmdb_ci_cloud_webserver\]]

{#cloud-disco-aws-data-collected__table_ar5_2gd_4db}  
{#cloud-disco-aws-data-collected__table_twm_drg_dtb__entry__3}

| Label | Field Name | Description |
|-|-|-|
| Name | name | The name of the kube-controller-manager leader. |
| Port | port | The identifier for the Kubernetes apiserver port. |
| Kubernetes UID | k8s_uid | The unique identifier for the Kubernetes Cluster. |
| Vendor | vendor | The vendor of the Kubernetes Cluster. |
| Fully qualified domain name | fqdn | The fully qualified domain name of the Kubernetes apiserver. |
[Table 18. Kubernetes Clusters \[cmdb_ci_kubernetes_cluster\]]

{#cloud-disco-aws-data-collected__table_twm_drg_dtb}
**Related concepts**   

* [Agent Client Collector Discovery](https://www.servicenow.com/docs/edhre6~2pn1oGWgUK2rrGQ "Discover CIs in your environment by using Agent Client Collector for Visibility Content (ACC-VC) Discovery. ACC-VC works with both horizontal IP-based Discovery, and you can also use push-based Discovery.")  
**Related reference**   

* [AWS discovery using patterns](https://www.servicenow.com/docs/1RHwXDhXziXfmCJyQkKV8w "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.")  
**Related topics**   

* [Service Graph Connector for AWS](https://www.servicenow.com/docs/access?context=cmdb-integration-aws-sg&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US)