---
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 Resource Inventory
# AWS Resource Inventory discovery with Patterns {#ariaid-title1}
Release version: Australia
Updated March 12, 2026
 3 minutes to read
Summarize
 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 Resource Inventory discovery with Patterns
ServiceNow Discovery and Service Mapping applications enable customers to discover and map AWS resources through the AWS Config Service using the AWS Resource Inventory pattern.
This pattern targets AWS resources without dedicated patterns, such as AWS Lambda and EC2, and operates on ServiceNow releases London (Patch 8), Madrid (Patch 2), or later.
Show full answer Show less
To leverage this functionality, customers may need to update to the latest Discovery and Service Mapping Patterns application from the ServiceNow Store.
## Key Features
* **AWS Resource Inventory pattern:** Discovers AWS resources accessible via AWS Config Service APIs, including resource tags.
* **Resource Inclusion List:** Allows customers to fine-tune discovery by specifying which AWS resource types to include, preventing duplicate discovery if custom patterns exist.
* **API Integration:** Uses AWS Config and Tagging APIs to retrieve resource data and tags during discovery with specified headers and request formats.
* **Application Scope:** The pattern operates within the Discovery and Service Mapping Patterns scope to maintain proper configuration and updates.
* **Cloud Inventory Resource Inclusion List management:** Customers can add or remove resource types to tailor discovery to their environment, noting that customization requires manual maintenance after updates.
## Prerequisites and Configuration
* Create AWS credentials and a dedicated AWS cloud service account for discovery (management account only, not sub-accounts).
* Schedule full AWS discovery or run the specific AWS Resource Inventory pattern as needed.
* Manage the Resource Inclusion List to align discovery with your custom patterns and prevent redundant data collection.
* Set the application scope to Discovery and Service Mapping Patterns when configuring the inclusion list and discovery patterns.
## Data Collected and Relationships
The discovery process collects key details for each AWS resource, including:
* **objectid:** Typically the Amazon Resource Name (ARN) identifying the resource.
* **name:** The resource's name.
* **resourcetype:** The AWS asset type as defined by the JSON response.
* **description:** Brief details on how the CI is populated.
Relationships established include the resource being **hosted on** a Logical Datacenter CI, enabling clear dependency mapping within the CMDB.
## Practical Benefits for ServiceNow Customers
By implementing AWS Resource Inventory discovery with patterns, customers can:
* Gain comprehensive visibility into AWS assets that lack dedicated discovery patterns.
* Customize discovery scope to avoid duplication and maintain an accurate CMDB.
* Leverage standardized APIs for consistent, up-to-date resource and tag information.
* Integrate AWS resource data seamlessly into ServiceNow's Discovery and Service Mapping frameworks to support IT operations and service management.
The ServiceNow
Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Discovery uses the AWS Resource Inventory pattern to discover the resources available through AWS. Use this pattern for AWS resources which do not have a dedicated pattern, such as AWS Lambda or EC2. This pattern is limited to resources that are available from AWS Config Service, as described in the [AWS Config Developer Guide](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html).
You can use this pattern on the ServiceNow platform using London (Patch 8), Madrid (Patch 2), or later releases.
## Request apps on the Store {#aws-resource-inventory__section_hly_lql_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).{#aws-resource-inventory__inline-send-to-store}
## Prerequisites {#aws-resource-inventory__section_ony_yhb_2jb}
* Create AWS credentials.
* Create an AWS cloud service account.
You can use only the AWS management service account for discovery, not its sub-accounts.
Note:
The Cloud Discovery user interface refers to member accounts as sub-accounts.
* Discover AWS Datacenters (LDC)
* Schedule a full AWS discovery or use a specific inventory pattern
* Fine-tune AWS resource discovery using the Resource Inclusion List.
If your deployment has custom patterns for AWS discovery, ensure that you do not discover AWS resources twice.
1. Ensure that the application scope is Discovery and Service Mapping Patterns:
1. Navigate to SettingsDeveloper.
2. Select Discovery and Service Mapping Patterns from the Application list.
{#aws-resource-inventory__ol_nfr_g2l_d3b}
2. Navigate to System DefinitionsTables.
3. Open the Cloud Inventory Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table.
4. Under Related Links, click Show List.
5. Select resource types for which you have custom patterns, and select Delete from the Actions on selected rows list.
{#aws-resource-inventory__ol_d1v_kb2_d3b}
The Cloud Inventory Resource Inclusion List is predefined with common services. You can expand the list with additional resource types that you want the pattern to discover. The names of these resource types must conform to the appropriate vendor naming conventions.
Note:
When you modify the out-of-the-box inclusion list, it is no longer updated automatically in application updates. You need to maintain the customized list on your own.
1. Open the Cloud Inventory Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table.
2. Click New.
3. Fill in the form, and then click Submit.{#aws-resource-inventory__table_a5z_112_fkb__entry__2}
| Field | Description |
|-|-|
| Cloud Vendor | The vendor of the resource type: AWS. |
| Resource Type | The AWS resource type value. For example, AWS::CloudWatch::Alarm. |
| Application | The application scope: Discovery and Service Mapping Patterns. |
[ ]
{#aws-resource-inventory__table_a5z_112_fkb}
{#aws-resource-inventory__ol_qrg_wzd_fkb}
The changes are applied the next time you run the pattern.
* To discover the resources that support the AWS Config service, the pattern uses API: https://config.\[AWS region\].amazonaws.com. It specifies the resource type in the API request using the following format: `{"resourceType":"AWS::[RESOURCE]::[TYPE]"}`
The
POST method requires the following headers:
* X-Amz-Target - StarlingDoveService.ListDiscoveredResources
* Accept - application/json
* Content-Type - application/x-amz-json-1.1
{#aws-resource-inventory__ul_rjx_xs3_2jb}
* To discover the resource tags for resources that support tags, the pattern uses API: https://tagging.\[AWS region\].amazonaws.com. It specifies the resource type in the API request using the following format: `{"ResourceTypeFilters": ["[resource]:[type]"]}`
The POST method requires the following headers:
* X-Amz-Target - ResourceGroupsTaggingAPI_20170126.GetResources
* Accept - application/json
* Content-Type - application/x-amz-json-1.1
{#aws-resource-inventory__ul_t1y_5sb_2jb}
{#aws-resource-inventory__ul_mcs_yvb_2jb}
## Data collected by Discovery during horizontal discovery {#aws-resource-inventory__section_jh3_yfc_2jb}
{#aws-resource-inventory__table_td3_psz_42b__entry__2}
| Table and field | Description |
|-|-|
| Main CI \[cmdb_ci_cmp_resource\] ||
| object_id | The ID of the item. This is typically the Amazon Resource Name (ARN). |
| name | Name of the resource. |
| resource_type | The asset resource type, based on the contents of the JSON file. |
| description | Short description of how the CI is populated. |
[ ]
{#aws-resource-inventory__table_td3_psz_42b}
## CI relationships {#aws-resource-inventory__section_gfx_zw4_zhb}
The AWS Resource Inventory pattern creates the following CI relationship:{#aws-resource-inventory__table_hfx_zw4_zhb__entry__3}
| CI | Relationship | CI |
|-|-|-|
| Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on :: Hosts | Logical Datacenter \[cmdb_ci_logical_datacenter\] |
[ ]
{#aws-resource-inventory__table_hfx_zw4_zhb} The following is a dependency view of the collected data flow.
Figure 1. AWS Resource Inventory dependency view
*[\>]: and then