---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set the AWS SSM command wait time

# Set the AWS SSM command wait time {#ariaid-title1}

Release version: Brazil  
Updated September 17, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Increase the wait time for AWS Systems Manager (AWS SSM) commands to support Server CI creation on slow-responding EC2 instances.

## Before you begin

* Verify that the sn_itom_pattern.aws_cloud_discovery_populate_server_ci system property is set to <kbd class="ph userinput">true</kbd>. For more information, see [Configure Server CI creation during AWS cloud discovery](https://www.servicenow.com/docs/gP4KtfWjjv0BCUV9TRdpNQ "Create Windows Server or Linux Server configuration items (CIs) during AWS cloud discovery by enabling the sn_itom_pattern.aws_cloud_discovery_populate_server_ci system property.").
* Verify that you have at least version 1.35.1 of Discovery and Service Mapping Patterns.

{#set-aws-ssm-server-timeout__ul_pty_sfl_pkc}

Role required: discovery_admin

## About this task

By default, the MID Server waits 30 seconds (30000 ms) before checking whether the Server CI is created on a Windows or Linux EC2 instance. If instances in your environment are slow to respond, Server CIs may not be created. Increase the sn_itom_pattern.discover_aws_server_command_initial_wait_ms
MID Server property value to provide more time before the first status check.

## Procedure

1. Navigate to AllMID ServerProperties.
2. In the Name column, search for <kbd class="ph userinput">sn_itom_pattern.discover_aws_server_command_initial_wait_ms</kbd>.
3. Select the sn_itom_pattern.discover_aws_server_command_initial_wait_ms MID Server property.
4. In the Value field, enter the wait time in milliseconds.  
   The default value is <kbd class="ph userinput">30000</kbd> (30 seconds). The property accepts any positive integer.
5. Select Update.
{#set-aws-ssm-server-timeout__steps_h4w_fbl_pkc}

## Result

The MID Server applies the updated wait time when running the next SSM commands during AWS Cloud Discovery Server CI creation.

## What to do next

Run AWS Cloud Discovery again to apply the change.
**Related tasks**   

* [Configure Server CI creation during AWS cloud discovery](https://www.servicenow.com/docs/gP4KtfWjjv0BCUV9TRdpNQ "Create Windows Server or Linux Server configuration items (CIs) during AWS cloud discovery by enabling the sn_itom_pattern.aws_cloud_discovery_populate_server_ci system property.")  
**Related reference**   

* [AWS discovery using patterns](https://www.servicenow.com/docs/Y0yjdHKR~_I76hi21l9C4A "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")
* [AWS Linux Server pattern-based discovery](https://www.servicenow.com/docs/bwcNwjZLVgFtuNIlS6kZFw "Discovery and Service Mapping Patterns finds AWS Linux Server configuration items (CIs) in your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")
* [AWS Windows Server pattern-based discovery](https://www.servicenow.com/docs/gEhm2x_NAH_KGzeU_Yy31g "Discovery and Service Mapping Patterns finds AWS Windows Server configuration items (CIs) in your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")

*[\>]: and then