From 55747c9dc4ce1d274e44cf7e587be2869eea7bb0 Mon Sep 17 00:00:00 2001 From: Jesse Turner Date: Thu, 16 Apr 2026 21:28:23 +0000 Subject: [PATCH] docs: document executionRoleArn in runtime spec The runtime spec table in configuration.md omitted the existing optional executionRoleArn field, leading users (see issue #870) to believe the CLI had no way to bring their own IAM execution role. The field is already supported in the schema. Confidence: high Scope-risk: narrow --- docs/configuration.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/configuration.md b/docs/configuration.md index 985893652..6e42c101a 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -191,6 +191,7 @@ on the next deployment. | `authorizerConfiguration` | No | JWT authorizer settings (for `CUSTOM_JWT`) | | `requestHeaderAllowlist` | No | Headers to forward to the agent | | `lifecycleConfiguration` | No | Runtime session lifecycle settings (idle timeout, max lifetime) | +| `executionRoleArn` | No | ARN of an existing IAM execution role (skips CDK-managed role) | | `tags` | No | Agent-level tags | ### Runtime Versions