Data collected for Amazon AWS Cloud Discovery
Summarize
Summary of Data collected for Amazon AWS Cloud Discovery
Amazon AWS Cloud Discovery in ServiceNow collects detailed information about cloud resources within AWS datacenters. This enables customers to maintain an accurate and up-to-date Configuration Management Database (CMDB) of their AWS infrastructure. To discover some resources, customers must ensure they have the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
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 a discovery schedule within the Cloud Discovery Workspace to automate the data collection process.
- Confirm REST API permissions by downloading the Cloud Discovery patterns spreadsheet. This spreadsheet provides required user permissions, pattern details, CI classes, and links to vendor documentation.
- Test AWS REST APIs using tools like Postman, guided by ServiceNow knowledge base articles.
- Check periodically for quarterly updates to Cloud Discovery patterns to maintain coverage of new AWS resources.
Data Collected
The discovery process gathers extensive data across multiple AWS resource types, which populate corresponding CMDB tables. Key resource categories include:
- AWS Datacenters: Region and object identification.
- Availability Zones: Zone names.
- Virtual Machine Instances: Attributes such as state, CPUs, memory, disks, network adapters, and instance IDs.
- Compute Security Groups: State and identification.
- Images and Hardware Types: OS templates, guest OS, device types, vCPUs, memory, and storage details.
- Storage Volumes: Size, type, and state.
- Cloud Networks and Subnets: Names, states, CIDR blocks, and status.
- Cloud Management Network Interfaces: MAC manufacturer, netmask, status.
- Load Balancers, Resource Groups, Public IP Addresses, and Storage Accounts: Identification, state, and relevant metadata.
- DNS Aliases and Names: Categories, IP addresses, and statuses.
- Cloud Databases: Database names, types, FQDNs, states, TCP ports, instance classes, and backup configurations.
- Cloud Web Servers: Vendor, operational status, install status, and FQDN.
- Kubernetes Clusters: Cluster identifiers, ports, vendor info, and FQDNs.
Practical Benefits for ServiceNow Customers
By implementing AWS Cloud Discovery, customers gain comprehensive visibility into their AWS cloud assets within the ServiceNow platform. This enables improved asset management, compliance, and operational efficiency. The detailed, structured data helps maintain an accurate CMDB, supports service mapping, and facilitates automated workflows based on real-time AWS configurations.
Related Resources
- Agent Client Collector and Discovery documentation for extending data collection capabilities.
- Service Graph Connector for AWS for enhanced integration and data visualization.
- Specific discovery patterns and AWS discovery reference materials to deepen understanding and customization.
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
Visit the ServiceNow Store 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.
Prerequisites
- Verify that the applications are up to date.
-
- Discovery and Service Mapping Patterns.
- CMDB CI Class Models.
- Visibility Content.
- Configure a discovery schedule
- Create a discovery schedule in Cloud Discovery Workspace
Verify the REST API Permissions
Download the Cloud Discovery patterns spreadsheet 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.
Data collected for AWS Cloud Discovery
The following tables show examples of data collected during AWS Cloud Discovery.
| Label | Field Name |
|---|---|
| Name | name |
| Region | region |
| Object ID | object_id |
| Label | Field Name |
|---|---|
| Name | name |
| 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 |
| Label | Field Name |
|---|---|
| Name | name |
| Object ID | object_id |
| State | state |
| 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 |
| Label | Field Name |
|---|---|
| Name | name |
| vCPUs | vcpus |
| Memory MB | memory_mb |
| Local Storage GB | local_storage_gb |
| Label | Field Name |
|---|---|
| Name | name |
| State | state |
| Object ID | object_id |
| Storage type | storage_type |
| Size | size |
| Label | Field Name |
|---|---|
| Name | name |
| State* | state |
| CIDR* | cidr |
| Label | Field Name |
|---|---|
| Name | name |
| Status | status |
| CIDR | cidr |
| Label | Field Name |
|---|---|
| Name | name |
| Netmask | netmask |
| MAC Manufacturer | mac_manufacturer |
| Status | install_status |
| Label | Field Name |
|---|---|
| Name | name |
| Object ID | object_id |
| State | state |
| Label | Field Name |
|---|---|
| Name | name |
| Object ID | object_id |
| State | state |
| Label | Field Name |
|---|---|
| Name | name |
| Object ID | object_id |
| Public IP address | public_ip_address |
| Public DNS | public_dns |
| Label | Field Name |
|---|---|
| Name | name |
| Object ID | object_id |
| Sku Name | sku_name |
| State | state |
| 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 |
| 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:
|
| 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. |
| Label | Field Name |
|---|---|
| Name | name |
| Install status | install_status |
| Vendor | vendor |
| Fully qualified domain name | fqdn |
| Operational status | operational_status |
| State | state |
| 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. |