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

# AWS tag discovery with Patterns {#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 AWS tag discovery with Patterns

ServiceNow's Discovery and Service Mapping applications use specialized patterns to discover AWS resource tags and populate the CMDB with detailed tag information.
These tag discovery patterns complement existing AWS resource discovery patterns available from the ServiceNow Store.
Customers may need to update to the latest Discovery and Service Mapping Patterns application to leverage this functionality fully.
The patterns enable discovery of tags across a broad set of AWS resource types, enhancing visibility and configuration management within the CMDB.
Show full answer Show less  

## Key Features

* **Wide AWS Resource Coverage:** Tag discovery supports numerous AWS CI types including ACLs, API Gateways, Load Balancers, Cognito, DynamoDB, Lambda functions, S3 storage, Virtual Servers, VPN connections, and many more.
* **Pattern-Based Tag Discovery:** The tag discovery pattern extends existing AWS resource discovery patterns to specifically collect tags, allowing precise filtering and association of tags to the correct CI types.
* **Cloud API Integration:** Uses the AWS Resource Groups Tagging API via a "Cloud Rest Call" to fetch tags filtered by resource type, ensuring accurate and efficient data collection.
* **Parsing and Relationship Mapping:** Parses resource names from Amazon Resource Names (ARNs) when necessary, and establishes relationships between tags and their corresponding AWS resources within the CMDB.
* **Discovery Scheduling and Credentials:** Requires AWS credentials configured with appropriate read-only permissions and a discovery schedule set up in the ServiceNow Cloud Discovery Workspace for automated tag collection.

## Practical Application for ServiceNow Customers

By implementing AWS tag discovery patterns, customers gain enhanced configuration management by automatically importing tags for a wide array of AWS resources into the CMDB. This enables better asset tracking, governance, and service mapping accuracy. Customers should ensure proper AWS credentials and permissions are configured, and that discovery schedules are created for their AWS accounts. Understanding how the patterns filter and parse tag data helps troubleshoot and customize tag discovery behavior if needed.

## What to Expect

* Updated CMDB entries enriched with AWS tag metadata for multiple resource types.
* Improved accuracy in service maps and dependency views through comprehensive tag data.
* Automated, repeatable discovery runs driven by configured schedules and AWS API integration.
* Support for resolving tags even when resource identification requires custom parsing of ARNs.  
The ServiceNow
Discovery and Service Mapping applications can use patterns to discover the tags for AWS resources and configuration item (CI) types. They then populate the CMDB with these discoveries. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
This tag-specific discovery pattern is in addition to the other AWS patterns available on the ServiceNow Store.This pattern extends the ones used for discovering the respective AWS resources.  
Discovery populates the CMDB with tags for the following AWS patterns and CI types:

* Amazon AWS - ACL (LP) \[cmdb_ci_network_acl\]
* Amazon AWS API Gateway \[cmdb_ci_cloud_gateway\]
* Amazon AWS - Application and Network LB (LP) \[cmdb_ci_cloud_load_balancer\]
* Amazon AWS Application and Network LBs Events
* Amazon AWS - Classic LB (LP) \[cmdb_ci_cloud_load_balancer\]
* Amazon AWS Classic LB Events
* Amazon AWS Cognito \[cmdb_ci_cloud_authentication\]
* Amazon AWS - Customer Gateway (LP) \[cmdb_ci_customer_gateway\]
* Amazon AWS DB Cluster
* Amazon AWS DynamoDB \[cmdb_ci_dynamodb_table\]
* Amazon AWS ElastiCache
* Amazon AWS - ECS \[cmdb_ci_cloud_service_account\]
* Amazon AWS - Executable Template (LP) \[cmdb_ci_os_template\]
* Amazon AWS - Host (LP)
* Amazon AWS - Internet Gateway (LP)
* Amazon AWS keyspace
* Amazon AWS - Key Pair (LP)
* Amazon AWS Lambda \[cmdb_ci_cloud_function\]
* Amazon AWS - LB Pool (LP)
* Amazon AWS - NAT Gateway (LP)
* Amazon AWS - Network (LP)
* Amazon AWS Network Events
* Amazon AWS - NIC (LP)
* Amazon AWS - Owned Template (LP)
* Amazon AWS - Public IP Address (LP)
* Amazon AWS Redshift
* Amazon AWS Relational Database Service \[cmdb_ci_cloud_database\]
* Amazon AWS Resource Inventory
* Amazon AWS - Route Table (LP)
* Amazon AWS S3 \[cmdb_ci_cloud_object_storage\]
* Amazon AWS - Security Group (LP)
* Amazon AWS Security Group Events
* Amazon AWS Serverless Database
* Amazon AWS - Storage (LP)
* Amazon AWS Storage Events
* Amazon AWS sub account discovery
* Amazon AWS - Subnet (LP)
* Amazon AWS - Virtual Server (LP)
* Amazon AWS Virtual Server Events
* Amazon AWS - VPN Connections (LP)
* Amazon AWS - VPN Gateway (LP)

{#aws-discovery-pattern__ul_cwm_pns_vhb}  
Note:  
For more information about the tags and patterns for each of these resources, see the documentation for the specific AWS resource.

## Request apps on the Store {#aws-discovery-pattern__section_gvb_cql_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-discovery-pattern__inline-send-to-store}

## Prerequisites {#aws-discovery-pattern__section_z5d_lm1_whb}

AWS Credentials
:
    * On the ServiceNow AI Platform, configure AWS credentials, using a secret key and an access key.
    * Have an Amazon Account ID. Use the Account ID as it appears in the AWS Management Console. You can run Discovery from the service account form.
    * Set read-only permissions for the following URL: https//tagging.\<region\>.amazonaws.com.
    {#aws-discovery-pattern__ul_avd_lm1_whb}

Discovery schedule
:   Create a schedule for the relevant AWS service account. For more information, see [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.").

## Pattern tasks {#aws-discovery-pattern__section_pk2_sjy_xhb}

When discovering AWS tags, the pattern completes the following high-level tasks:

* Sets the Resource Type filter: Filters the tags to only those tags related to the pattern CI type.
* Initiates the Cloud API call: The API call to the cloud environment that collects the tags and parses their attributes in the Tags table.
* Parses the resource name from the Amazon Resource Name (ARN). Each Amazon resource is assigned a name and a unique identifier.  
  Note:  
  Parsing the resource name is needed only for patterns where the main identification section does not work with the ARN of the AWS resource. When that is the case, a relation attribute has to be parsed from the AWS ARN.
* Includes references to cloud resource type. Establishes the relationship between the tag and the cloud resource type.
{#aws-discovery-pattern__ul_kg4_2m1_whb}

## Cloud Rest Call {#aws-discovery-pattern__section_ctk_zpz_vhb}

The pattern includes an API called "Cloud Rest Call" Post Call used to collect the following data:

* API URL used to retrieve the data --- "https://tagging." + $ldc\[1\].object_id + ".amazonaws.com/"
* API Body --- "{\\"ResourceTypeFilters\\":\[\\"" + $resource_type + "\\"\]}"
* Headers --- "Content-Type:application/x-amz-json-1.1,X-Amz-Target:ResourceGroupsTaggingAPI_20170126.GetResources"

{#aws-discovery-pattern__ul_inz_vrz_vhb}

This data displays as shown in the following window.
Figure 1. Data from Cloud Rest Call

## Data collected by Discovery during horizontal discovery {#aws-discovery-pattern__section_fgj5_j3q_fdb}

The pattern collects the following data during horizontal discovery:  
{#aws-discovery-pattern__table_olk_1pq_f56b__entry__2}

| Table and field | Additional information |
|-|-|
| CI type \[cmdb_key_value\] ||
| Key | Tag key |
| Value | Tag value |
| Object_id | Unique resource ID that identifies the resource in the AWS console. |
| Class model \[cmdb_key_value\] ||
| Extends table | Not applicable |
| Identifier -- Object_id | Related entries to cloud resources |
| Metadata rules | Not applicable |
[ ]

{#aws-discovery-pattern__table_olk_1pq_f56b}

This data is displayed as shown in the following window:
Figure 2. Data collected during horizontal discovery AWS discovery pattern uses the following EVAL:

    var rtrn;
    var name = ${cmdb_key_value[].object_id}
    name = name.substring(name.lastIndexOf("restapis/")+9,name.lastIndex);
    name = name.substring(0,name.indexOf("/"));
    rtrn = name;

Similar EVALS are available for patterns where the main identification section does not include ARN information in the main CI type table. When this information is not available, the Tag Extension section must parse a unique ARN used to establish the relationship to the related cloud resource.

