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


---

# Create a serverless discovery schedule

# Create a serverless schedule for Amazon ECS discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated May 5, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Create a serverless schedule to discover Amazon Elastic Container Service (Amazon ECS) and Amazon Elastic Container Registry (ECR) resources in a standalone discovery.

## Before you begin

Verify you have an AWS service account ID and have created AWS credentials. For more information, see the prerequisites section in [Amazon ECS resource discovery with Patterns](https://servicenow-prod.fluidtopics.net/tRIJbSQlM~dhgQQzyIz54g "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.").

Role required: discovery_admin

## About this task

Discovering ECR resources requires running the Amazon AWS - ECS pattern before using Aqua Trivy to scan container images. To discover only ECS and ECR resources without performing a full AWS pattern discovery, create a serverless discovery schedule using the Amazon AWS - ECS pattern.

## Procedure

1. Navigate to AllDiscoveryDiscovery Schedules.
2. Create the discovery schedule record.
   1. Select New.
   2. On the form, fill in the fields.  
      {#create-serverless-schedule-ecs__table_fx4_nhp_ffc__entry__2}

      | Field | Description |
      |-|-|
      | Name | Unique name for this discovery schedule. |
      | Discover | Scan type, which should be Serverless. |
      | MID server | Name of the MID Server to use for this schedule. |
      | Active | Enables this schedule for discovery. |
      | Run | Determines the run schedule of the discovery. |
      [Table 1. Discovery Schedule New record form]

      {#create-serverless-schedule-ecs__table_fx4_nhp_ffc}
   3. Select Submit.
   {#create-serverless-schedule-ecs__substeps_ylk_3hp_ffc}
3. Create the execution pattern.
   1. In the Discovery Schedules page, select the record you created.
   2. In the Serverless Execution Patterns tab, select New.
   3. On the form, fill in the fields.  
      {#create-serverless-schedule-ecs__table_jnq_13p_ffc__entry__2}

      | Field | Description |
      |-|-|
      | Name | Descriptive name for this record. |
      | Pattern | Pattern to be used for this schedule, which should be Amazon AWS - ECS. |
      | Proxy Host | Fully qualified domain name of the machine on which you're installing the proxy server, which should be Global. |
      | Active | Enables this schedule for discovery. |
      [Table 2. Serverless Execution Pattern New record form]

      {#create-serverless-schedule-ecs__table_jnq_13p_ffc}
   4. Select Submit.
   {#create-serverless-schedule-ecs__substeps_jcq_vhp_ffc}
4. Set the pattern launcher parameters.
   1. In the Discovery Pattern Launcher Parameters tab, select the record you created.
   2. On the form, fill in the fields.  
      {#create-serverless-schedule-ecs__table_gf1_gkp_ffc__entry__2}

      | Parameter | Value |
      |-|-|
      | cloud_account_id | AWS cloud service account ID. |
      | cloud_cred_id | Sys_id of the AWS credentials you created on the ServiceNow AI Platform. |
      | cloud_datacenter_type | Name of the AWS Datacenter table, which should be cmdb_ci_aws_datacenter. |
      [ ]

      {#create-serverless-schedule-ecs__table_gf1_gkp_ffc}
   3. Select Submit.
   {#create-serverless-schedule-ecs__substeps_arb_ckp_ffc}

## What to do next

Either execute discovery immediately by selecting Discover now or wait until the predefined schedule triggers the discovery.
**Related tasks**   

* [Scan container images](https://servicenow-prod.fluidtopics.net/7~3F3xLe_VZJrg5pPbWiAQ "Enable container image scanning using the Aqua Trivy tool.")  
**Related reference**   

* [Amazon ECS resource discovery with Patterns](https://servicenow-prod.fluidtopics.net/tRIJbSQlM~dhgQQzyIz54g "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.")

*[\>]: and then