---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Amazon ECS resource

# Amazon ECS resource discovery with Patterns {#ariaid-title1}

* Release version: Yokohama
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read

The ServiceNow
Discovery application uses the Amazon
AWS - ECS pattern to find resources managed by the Amazon Elastic Container Service (Amazon ECS). This includes resources that are run on the Fargate launch type. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Amazon ECS is a highly scalable, fast, container management service that makes it easy to run, stop, and manage Docker containers. AWS Fargate is a compute engine for Amazon ECS that enables AWS customers to run containers without having to manage servers or clusters.

Discovery uses the Amazon
AWS - ECS pattern to run horizontal discovery.

Starting with Discovery and Service Mapping Patterns version 1.18.0, the Amazon
AWS - ECS pattern supports the discovery of Amazon Elastic Container Registry (Amazon ECR) images. For more information on container scanning, see [Scan container images](https://www.servicenow.com/docs/7~3F3xLe_VZJrg5pPbWiAQ "Enable container image scanning using the Aqua Trivy tool.").

Starting with Discovery and Service Mapping Patterns version 1.31.0, you can choose to discover Docker image CIs only, without discovering Docker container CIs. Check your entitlements to determine whether you have access to 2026 Packaging SKU. For more information, see [Disable Docker container CI discovery](https://www.servicenow.com/docs/XoHm99icj0c_aFRa6Yac5Q "Configure Docker discovery to collect image CIs only, instead of both image and container CIs.").{#aws-ecs-fargate-discovery__check-entitlements-2026-container-packaging}

## Request apps on the Store {#aws-ecs-fargate-discovery__section_dbb_kgm_rlb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#aws-ecs-fargate-discovery__inline-send-to-store}

## Amazon ECS data model {#aws-ecs-fargate-discovery__section_data_model}

The Amazon
AWS - ECS pattern introduces the following CI classes that extend an existing CMDB class.  
{#aws-ecs-fargate-discovery__table_extends_ecs__entry__2}

| CI class | Extends from |
|-|-|
| AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] | Virtual Machine Object \[cmdb_ci_vm_object\] |
| AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] | Virtual Machine Object \[cmdb_ci_vm_object\] |
| AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] | Virtual Machine Object \[cmdb_ci_vm_object\] |
| AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] | Virtual Machine Object \[cmdb_ci_vm_object\] |
[Table 1. CI classes introduced by this pattern]

{#aws-ecs-fargate-discovery__table_extends_ecs}

## Prerequisites {#aws-ecs-fargate-discovery__section_tkn_fjm_njb}

Create AWS credentials with ECS resources viewing privileges
:
    In the AWS console, create AWS credentials with privileges to view ECS resources. For more information, see: <https://docs.aws.amazon.com/en_pv/AmazonECS/latest/userguide/get-set-up-for-amazon-ecs.html>.  
    Note:  
    The API requests use AWS Signature Version 4 to authenticate. When the correct credentials are provided, authentication is done internally for the Cloud API Call pattern steps.

Create AWS cloud credential records or use temporary credentials
:   In the ServiceNow AI Platform, create AWS credential records. You can also use a temporary credential generated by the AWS Security Token Service (AWS STS) for IAM roles. For more information, see [Cloud credentials](https://www.servicenow.com/docs/access?context=r_CloudManagementCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US)

Create AWS cloud service accounts
:
    * In the ServiceNow AI Platform, create AWS cloud service accounts using permanent or temporary AWS credentials. For more information, see [Set up AWS service accounts](https://www.servicenow.com/docs/UO4WIwvrPVWckI9LeWzMRg "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Amazon Web Services (AWS) service accounts.").
    * In the Cloud Service Account record, select Discover Datacenters to find AWS Datacenters (LDCs) for the configured AWS cloud service account.
    {#aws-ecs-fargate-discovery__ul_gvb_h5s_bcc}

Schedule an AWS discovery
:   In the ServiceNow AI Platform, schedule either a full AWS pattern discovery or only an ECS pattern discovery.

    * For more information on scheduling a cloud discovery, see [Create a discovery schedule in Cloud Discovery Workspace](https://www.servicenow.com/docs/4egAp8rafm6~FSeRVUzHTg "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.").
    * For more information about creating a serverless schedule for Amazon ECS discovery, see [Create a serverless schedule for Amazon ECS discovery](https://www.servicenow.com/docs/OhoTAPkbHYPmVlO3BUSQ4A "Create a serverless schedule to discover Amazon Elastic Container Service (Amazon ECS) and Amazon Elastic Container Registry (ECR) resources in a standalone discovery.").
    {#aws-ecs-fargate-discovery__ul_fvt_jmp_ffc}

Verify configuration of VM Object record to find the resource Tags
:
    To enable the pattern to find the resource Tags, the parent ECS table (VM Object) must have a related entry for the cmdb_key_value table:

    1. In the ServiceNow AI Platform navigation bar, navigate to AllConfigurationIdentification/Reconciliation, and select CI Identifiers.
    2. Search for and open the VM Object record.
    3. Select the Related Entries tab and make sure it's configured as shown in the VM Object Related Entry figure. If it isn't, specify a new related entry: In the Related Entries related list, select New, fill out the form, and then select Submit.Figure 1. VM Object Related Entry   

    {#aws-ecs-fargate-discovery__ol_lg1_y5s_bcc}

## Verify the REST API Permissions {#aws-ecs-fargate-discovery__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.{#aws-ecs-fargate-discovery__cloud-discovery-api-paragraph}
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 by Discovery during horizontal discovery {#aws-ecs-fargate-discovery__section_c2g_lxn_njb}

Discovery populates the data in the CMDB when running the Amazon
AWS - ECS pattern.  
{#aws-ecs-fargate-discovery__table_urz_qcr_bcc__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The Amazon Resource Name (ARN) that identifies the cluster. |
| Name \[name\] | A user-generated string used to identify the cluster. |
| Registered Container Instances Count \[registered_container_instances_count\] | The number of container instances registered to the cluster. The status of these container instances can be either ACTIVE or DRAINING. |
[Table 2. AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\]]

{#aws-ecs-fargate-discovery__table_urz_qcr_bcc}  
{#aws-ecs-fargate-discovery__table_cvz_wcr_bcc__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The full ARN of the task definition. |
| Name \[name\] | The name of the family to which this task definition is registered. |
| Revision \[revision\] | The revision of the task in a particular family. This is the version number of the task definition in a family. |
| Network Mode \[network_mode\] | The Docker networking mode to use for the containers in the task. Valid values: None, bridge, awsvpc, host. |
| CPU \[cpu\] | The number of CPU units used by the task. |
| Memory \[memory\] | The amount of memory, in mebibyte (MiB), used by the task. |
[Table 3. AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\]]

{#aws-ecs-fargate-discovery__table_cvz_wcr_bcc}  
{#aws-ecs-fargate-discovery__table_v1d_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The ARN that identifies the task. |
| Name \[name\] | A user-generated string used to identify the task. |
| Launch Type \[launch_type\] | The launch type on which the task runs. |
| Operational status \[operational_status\] | The health status of the task, determined by the health of the essential containers in it. |
| CPU \[cpu\] | The number of CPU units used by the task, as stated in the task definition. |
| Memory \[memory\] | The amount of memory, in MiB, used by the task, as stated in the task definition. |
[Table 4. AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\]]

{#aws-ecs-fargate-discovery__table_v1d_xcr_bcc}  
{#aws-ecs-fargate-discovery__table_cng_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The ARN that identifies the service. |
| Name \[name\] | The name of the service. |
| Launch Type \[launch_type\] | The launch type on which the service runs. |
| Scheduling Strategy \[scheduling_strategy\] | The scheduling strategy to use for the service. |
[Table 5. AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\]]

{#aws-ecs-fargate-discovery__table_cng_xcr_bcc}  
{#aws-ecs-fargate-discovery__table_ubj_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Container id \[container_id\] | The ARN of the container. |
| Name \[name\] | The name of the container. |
| Status \[status\] | The last-known status of the container. |
| Operational status \[operational_status\] | The health status of the container. |
| CPU \[cpu\] | The number of CPU units set for the container. |
| Memory \[memory\] | The hard limit of memory, in MiB, set for the container. |
[Table 6. Docker Container \[cmdb_ci_docker_container\]]

{#aws-ecs-fargate-discovery__table_ubj_xcr_bcc}  
{#aws-ecs-fargate-discovery__table_wvn_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The ARN that identifies the virtual machine (VM) instance. Note: Complete Virtual Machine Instance information is discovered in a different EC2 cloud pattern. In Amazon ECS resource discovery, only the object_id is parsed to aid with the unique identification of the CI. |
[Table 7. Virtual Machine Instance \[cmdb_ci_vm_instance\]]

{#aws-ecs-fargate-discovery__table_wvn_xcr_bcc}  
{#aws-ecs-fargate-discovery__table_s2q_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | The Tag key. |
| Value \[value\] | The Tag value. |
| Configuration item \[configuration_item\] | References the discovered CI that the tag is associated with. |
[Table 8. Key Value \[cmdb_key_value\]]

{#aws-ecs-fargate-discovery__table_s2q_xcr_bcc}  
{#aws-ecs-fargate-discovery__table_dvt_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the Docker image. |
| Image Digest \[image_digest\] | Unique identifier for the Docker image. |
| Image ID \[image_id\] | 12-character length unique identifier for the Docker image. |
[Table 9. Docker Image \[cmdb_ci_docker_image\]]

{#aws-ecs-fargate-discovery__table_dvt_xcr_bcc}  
{#aws-ecs-fargate-discovery__table_ozw_xcr_bcc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Fully qualified name of the repository containing the Docker image. |
[Table 10. Container Repository \[cmdb_ci_container_repository\]]

{#aws-ecs-fargate-discovery__table_ozw_xcr_bcc} {#aws-ecs-fargate-discovery__table_tl1_ycr_bcc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | The Docker image tag. |
| Category \[category\] | Fully qualified name of the repository containing the Docker image. |
[Table 11. Container Repository Entry \[cmdb_ci_container_repository_entry\]]

{#aws-ecs-fargate-discovery__table_tl1_ycr_bcc}

On the Dependency Views map, you can see all discovered resources in your organization that are managed by Amazon ECS, and the relationships between them.

In this example, the AWS Cloud ECS Cluster CI is hosted on an AWS Datacenter. It runs two AWS Cloud ECS Tasks and two AWS Cloud ECS Services, and uses three Docker Containers.
Figure 2. Dependency Views sample map   

## CI relationships {#aws-ecs-fargate-discovery__section_c4s_fk4_njb}

The Amazon
AWS - ECS pattern creates the following relationships and references to support Amazon ECS resource discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table.  
{#aws-ecs-fargate-discovery__table_xl4_mk4_njb__entry__3}

| CI | Relationship | CI |
|-|-|-|
| AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Used by::Uses | AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] | Runs on::Runs | AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] |
| AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] | Uses::Used by | AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] |
| AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\]\* | Runs on::Runs | AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] |
| AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\]\* | Runs on::Runs | Virtual Machine Instance \[cmdb_ci_vm_instance\] |
| AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] | Runs on::Runs | Docker Container \[cmdb_ci_docker_container\] |
| AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] | Uses::Used by | AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] |
| AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] | Used by::Uses | AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] |
| AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] | Used by::Uses | AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] |
| Docker Container \[cmdb_ci_docker_container\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| Docker Container \[cmdb_ci_docker_container\] | Used by::Uses | AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] |
| Container Repository \[cmdb_ci_container_repository\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
| Container Repository Entry \[cmdb_ci_container_repository_entry\] | Hosted on::Hosts | Container Repository \[cmdb_ci_container_repository\] |
| Docker Image \[cmdb_ci_docker_image\] | Provisioned From::Provisioned | Container Repository Entry \[cmdb_ci_container_repository_entry\] |
| Docker Image \[cmdb_ci_docker_image\] | Instantiates::Instantiated by | Docker Container \[cmdb_ci_docker_container\] |
[Table 12. CI relationships]

{#aws-ecs-fargate-discovery__table_xl4_mk4_njb}

\*The launch type determines which relationship is created. For Fargate launch type tasks, the relationship is created with the AWS Cloud ECS Cluster. For EC2 launch type tasks, the relationship is created with the Virtual Machine Instance.  
{#aws-ecs-fargate-discovery__table_ci_references_ecs__entry__3}

| CI | Field | Referenced CI |
|-|-|-|
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] |
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Virtual Machine Instance \[cmdb_ci_vm_instance\] |
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] |
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] |
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] |
[Table 13. CI references]

{#aws-ecs-fargate-discovery__table_ci_references_ecs}

## AWS tag discovery {#aws-ecs-fargate-discovery__section_tag_discovery}

The Amazon
AWS - ECS pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table.  
{#aws-ecs-fargate-discovery__table_tag_discovery_ecs__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | The Tag key. |
| Value \[value\] | The Tag value. |
| Configuration item \[configuration_item\] | References one of the following CIs that the tag is associated with: * AWS Cloud ECS Cluster \[cmdb_ci_cloud_ecs_cluster\] * Virtual Machine Instance \[cmdb_ci_vm_instance\] * AWS Cloud ECS TaskDefinition \[cmdb_ci_cloud_ecs_task_definition\] * AWS Cloud ECS Task \[cmdb_ci_cloud_ecs_task\] * AWS Cloud ECS Service \[cmdb_ci_cloud_ecs_service\] {#aws-ecs-fargate-discovery__ul_tag_ci_refs} |
[Table 14. Key Value \[cmdb_key_value\]]

{#aws-ecs-fargate-discovery__table_tag_discovery_ecs}

*[\>]: and then