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


---

# Data collected for AWS

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

Release version: Australia  
Updated March 12, 2026  
![](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

The Amazon AWS Cloud Discovery functionality within ServiceNow collects detailed information about cloud resources hosted in AWS datacenters.
This data enables customers to maintain an accurate Configuration Management Database (CMDB) that reflects their cloud infrastructure.
To discover certain AWS resources effectively, customers may need to update to the latest Discovery and Service Mapping Patterns application available on the ServiceNow Store.
Show full answer Show less  
Using AWS Cloud Discovery, customers can schedule discovery jobs, verify REST API permissions, and utilize provided patterns to gather comprehensive data about their AWS environment. Regular updates to discovery patterns are released quarterly, ensuring that new or changed AWS resources can be discovered accurately.

## Prerequisites and Setup

* Ensure the following applications are current: Discovery and Service Mapping Patterns, CMDB CI Class Models, and Visibility Content.
* Create a discovery schedule within the Cloud Discovery Workspace to automate data collection.
* Verify that REST API permissions are correctly configured to allow discovery operations.
* Download the Cloud Discovery patterns spreadsheet, which details permissions needed, pattern names, CI classes, and vendor documentation for reference.
* Test AWS REST APIs using tools like Postman to validate connectivity and permissions before running discovery.

## Key Data Collected

The discovery process collects and populates a broad range of AWS resource data into corresponding CMDB tables, enabling comprehensive visibility and management. Key resource types and their attributes include:

* **AWS Datacenters:** Region, Object ID
* **Availability Zones:** Name
* **Virtual Machine Instances:** State, CPUs, Memory, Disks, Network Adapters, VM Instance ID
* **Compute Security Groups:** State, Object ID
* **Images (OS templates):** Guest OS, Root device type, Image source and type
* **Hardware Types:** vCPUs, Memory in MB, Local Storage in GB
* **Storage Volumes:** State, Storage type, Size
* **Cloud Networks and VMware vCenter Networks:** State, CIDR (except VMware vCenter networks)
* **Cloud Subnets:** Status, CIDR
* **Cloud Management Network Interfaces:** Netmask, MAC Manufacturer, Status
* **Cloud Load Balancers:** State, Object ID
* **Resource Groups:** State, Object ID
* **Public IP Addresses:** Public IP address, Public DNS
* **Storage Accounts:** SKU name, State
* **DNS Aliases and DNS Names:** Category, Status, IP address
* **Cloud Databases:** Type, Fully qualified domain name, State, TCP port(s), Category, Automated backups
* **Cloud WebServers:** Install status, Vendor, Fully qualified domain name, Operational status, State
* **Kubernetes Clusters:** Cluster name, API server port, Kubernetes UID, Vendor, Fully qualified domain name

## Benefits for ServiceNow Customers

* Automated and detailed discovery of AWS cloud resources supports accurate CMDB population and lifecycle management.
* Improved visibility into resource states, configurations, and relationships helps optimize cloud governance and compliance.
* Regular pattern updates ensure discovery remains current with AWS service changes and additions.
* Comprehensive data enables integration with Service Graph Connector for AWS and supports broader IT operations and service management workflows.  
Discovery collects information about cloud resources in AWS datacenters. Discovering some of these resources might 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) 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/AGFiYHPbJImTnaawWg~_hQ "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-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 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/xafPexa00Lf9KGUlPNVM~Q "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/NFaTlkGaSxMWb2bQPsCnCA "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources might 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=australia&pubname=australia-servicenow-platform&ft:locale=en-US)