From bc0f7d8249cc0cf317857af4f1a7cace18c43894 Mon Sep 17 00:00:00 2001 From: Jesus Osuna Date: Thu, 23 Oct 2025 12:11:35 -0300 Subject: [PATCH 1/3] add info about ssm execution timeout --- docs/manual/projects/node-execution/aws-ssm.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/manual/projects/node-execution/aws-ssm.md b/docs/manual/projects/node-execution/aws-ssm.md index 47e893f92..a69498541 100644 --- a/docs/manual/projects/node-execution/aws-ssm.md +++ b/docs/manual/projects/node-execution/aws-ssm.md @@ -196,6 +196,15 @@ The SSM File Copier can alternatively be configured on a per **Node Source** or Once the setup is complete, commands that are executed on the specified EC2s - either through the [**Commands**](/manual/06-commands.md#commands-tab-overview) tab or through the **Remote Command** step - will automatically execute through SSM. Similarly, scripts that are executed using the **Incline Script** Job step will take place using SSM with S3 as the pass-through mechanism. +### Execution Timeout Configuration +AWS SSM has a default execution timeout of 1 hour (3600 seconds). You can configure a custom timeout value using the **`ssm-execution-timeout`** property to allow longer-running commands and scripts. + +To set the execution timeout for all SSM executions in a project: +1. Navigate to **Project Settings** -> **Edit Configuration** -> **Default Node Executor**. +2. In the **AWS / SSM / Node Executor** configuration, add the **Execution Timeout** value in seconds. + +**Default Value**: If not specified, the execution timeout defaults to **3600 seconds (1 hour)**. + ## Using CloudWatch Logs (Optional) The example policies in the prior sections enable Runbook Automation to retrieve logs directly from SSM. However, these logs are truncated to 48,000 characters. To view logs that are longer than this limit, CloudWatch logs are used. From 0d27a0bfde0a1172bdf1b4cf58d6c5eb1bce976a Mon Sep 17 00:00:00 2001 From: Jesus Osuna <87494173+Jesus-Osuna-M@users.noreply.github.com> Date: Thu, 23 Oct 2025 12:13:20 -0300 Subject: [PATCH 2/3] Update docs/manual/projects/node-execution/aws-ssm.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/manual/projects/node-execution/aws-ssm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/projects/node-execution/aws-ssm.md b/docs/manual/projects/node-execution/aws-ssm.md index a69498541..b0aeebb14 100644 --- a/docs/manual/projects/node-execution/aws-ssm.md +++ b/docs/manual/projects/node-execution/aws-ssm.md @@ -194,7 +194,7 @@ The SSM File Copier can alternatively be configured on a per **Node Source** or ## Using SSM for Commands and Scripts Once the setup is complete, commands that are executed on the specified EC2s - either through the [**Commands**](/manual/06-commands.md#commands-tab-overview) tab or through the **Remote Command** step - will automatically execute through SSM. -Similarly, scripts that are executed using the **Incline Script** Job step will take place using SSM with S3 as the pass-through mechanism. +Similarly, scripts that are executed using the **Inline Script** Job step will take place using SSM with S3 as the pass-through mechanism. ### Execution Timeout Configuration AWS SSM has a default execution timeout of 1 hour (3600 seconds). You can configure a custom timeout value using the **`ssm-execution-timeout`** property to allow longer-running commands and scripts. From 8498cb2a1c05dd56dfc68bc4f9ce53a28e9e2437 Mon Sep 17 00:00:00 2001 From: Jesus Osuna Date: Thu, 23 Oct 2025 15:35:00 -0300 Subject: [PATCH 3/3] add how to add the new property to the node --- docs/manual/projects/node-execution/aws-ssm.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/manual/projects/node-execution/aws-ssm.md b/docs/manual/projects/node-execution/aws-ssm.md index b0aeebb14..99f69d50a 100644 --- a/docs/manual/projects/node-execution/aws-ssm.md +++ b/docs/manual/projects/node-execution/aws-ssm.md @@ -203,6 +203,12 @@ To set the execution timeout for all SSM executions in a project: 1. Navigate to **Project Settings** -> **Edit Configuration** -> **Default Node Executor**. 2. In the **AWS / SSM / Node Executor** configuration, add the **Execution Timeout** value in seconds. +To set the execution timeout on project config file: +**`project.ssm-execution-timeout=3600`** + +To set the execution timeout at node level, add the following node-attribute to the nodes by using the [Attribute Match](/manual/node-enhancers.md#attribute-match) +**`ssm-execution-timeout=3600`** + **Default Value**: If not specified, the execution timeout defaults to **3600 seconds (1 hour)**. ## Using CloudWatch Logs (Optional)