---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# AWS DataSync Task

# AWS DataSync Task pattern-based discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 DataSync Task pattern-based discovery

The AWS DataSync Task pattern-based discovery enables ServiceNow customers to automatically discover and map AWS DataSync Task resources within their AWS cloud environments.
This discovery process populates data into both CMDB and non-CMDB tables, providing detailed insights into DataSync Tasks for better cloud asset management.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The AWS DataSync Task discovery pattern is disabled by default and must be enabled to start discovery. Activating or deactivating patterns is fully supported starting with Visibility Content version 6.28.0, and patterns reset to the latest predefined version after upgrades while retaining previous active states.
* **Prerequisites:** Customers must verify AWS discovery prerequisites and ensure the relevant DataSync Task resources are not listed in the Resource Inclusion List table to avoid duplicate discovery.
* **GovCloud Support:** Discovery for AWS GovCloud (US) accounts requires configuring the AWS service account with a datacenter URL.
* **Data Population:** The discovery pattern populates detailed DataSync Task information into the following tables:
  * **Non-CMDB Table:** `cmdbawsdatasynctask` holds task-specific data including ARN, name, status, configuration item reference, and task mode.
  * **CMDB Table:** `cmdbcicloudappserver` stores DataSync Task as a configuration item with fields such as ARN, name, install and operational status, and resource type.
  * **Tagging:** AWS tags are collected and stored in the `cmdbkeyvalue` table, enabling tagging-based management and reporting.
* **CI Relationships:** The pattern establishes relationships between DataSync Task CIs, Cloud App Servers, and AWS Datacenters to accurately model the AWS infrastructure.

## Practical Benefits

By implementing the AWS DataSync Task discovery pattern, customers can achieve:

* Comprehensive visibility into AWS DataSync Task resources directly within the ServiceNow CMDB.
* Reduced manual effort and errors by automating discovery and data population for DataSync Tasks.
* Improved accuracy in cloud service mapping with established CI relationships.
* Flexible management of discovery patterns with upgrade-safe activation and deactivation.
* Enhanced tagging visibility for better resource categorization and governance.

## Next Steps

* Verify and fulfill AWS discovery prerequisites as outlined in the Amazon AWS Cloud components discovery documentation.
* Remove any relevant DataSync Task resources from the Resource Inclusion List table to prevent duplicate discovery.
* Enable the AWS DataSync Task pattern within the Discovery and Service Mapping Patterns application.
* Configure discovery schedules appropriately, especially for AWS GovCloud environments.
* Review discovered DataSync Task data in both CMDB and non-CMDB tables and utilize CI relationships for accurate service mapping.  
Discovery and Service Mapping Patterns finds AWS services on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Pattern-based discovery and mapping requirements {#aws-datasync-task__selection_ipy_53n_jfc}

Verify the AWS discovery prerequisites
:   For more information, see the prerequisites section in [Amazon AWS Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/nnBwzYmMo_kpTZpG3y5~xQ "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.").

Remove resources from the Resource Inclusion List table
:   Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource
    Inclusion List, see [Amazon Web Services (AWS) Resource Inventory](https://servicenow-prod.fluidtopics.net/U2bwxjeyIbyEXySOOJQkYA "The ServiceNow Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Enable the relevant pattern
:   The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#aws-datasync-task__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud
:   Discovering AWS GovCloud (US) accounts requires using a datacenter URL when setting up an AWS service account. For more information, see [Create AWS service accounts](https://servicenow-prod.fluidtopics.net/CvTA68TY3ph_FRR49RbdPg "Create AWS service accounts on the ServiceNow AI Platform to access your AWS account during AWS discovery.").
Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

## Data stored in non-CMDB tables {#aws-datasync-task__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Amazon AWS - DataSync Task - Extended Inventory (LP) pattern.

You can review the non-CMDB
AWS tables by navigating to AllConfigurationAWS. You can also search the navigation filter for the specific pattern name.  
{#aws-datasync-task__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Object Id \[object_id\] | The Amazon Resource Name (ARN) uniquely identifying the DataSync task. |
| Name \[name\] | The name assigned to the AWS DataSync task. |
| Status \[status\] | The current operational status of the DataSync task. |
| Configuration Item \[configuration_item\] | References the Cloud App Server \[cmdb_ci_cloud_appserver\] table. |
| Task Mode \[task_mode\] | The execution mode of the DataSync task. For example: one-time or scheduled. |
[Table 1. AWS DataSync - Task \[cmdb_aws_datasync_task\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - DataSync Task - Extended Inventory (LP) pattern.  
{#aws-datasync-task__entry__14}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The ARN uniquely identifying the DataSync task. |
| Name \[name\] | The name assigned to the AWS DataSync task. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Type \[type\] | Type of resource. The value is set to AWS::DataSync::Task. |
[Table 2. Cloud App Server \[cmdb_ci_cloud_appserver\]]

## CI relationships

The Amazon AWS - DataSync Task - Extended Inventory (LP) pattern creates these relationships to support AWS DataSync Task discovery.  
{#aws-datasync-task__entry__27}

| CI | Relationship | CI |
|-|-|-|
| Cloud App Server \[cmdb_ci_cloud_appserver\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| AWS DataSync - Task \[cmdb_aws_datasync_task\] | References | Cloud App Server \[cmdb_ci_cloud_appserver\] |
[ ]

## AWS tag discovery {#aws-datasync-task__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-datasync-task__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 3. Key Value \[cmdb_key_value\]]

{#aws-datasync-task__table_axq_spc_y2c}

*[\>]: and then