From 880254093c9448f57686723e3d84b90ffb52575b Mon Sep 17 00:00:00 2001 From: Quetzalli Date: Wed, 9 Sep 2026 21:28:39 +0200 Subject: [PATCH] DOC-425: Remove stale &&/||/redirection limitation from SSM docs Verified against localstack/localstack-pro:latest (2026-09-01): SSM Run Command invokes a real shell (sh -c) under the hood, so &&, ||, and > all work correctly today. This claim was left over from an earlier, more limited implementation. The adjacent claim about stdout/stderr not being captured on a non-zero exit code is still accurate and is kept (tracked separately as a feature request). Co-Authored-By: Claude Sonnet 5 --- src/content/docs/aws/services/ssm.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/src/content/docs/aws/services/ssm.mdx b/src/content/docs/aws/services/ssm.mdx index d1e7a320..36dd39bc 100644 --- a/src/content/docs/aws/services/ssm.mdx +++ b/src/content/docs/aws/services/ssm.mdx @@ -148,7 +148,6 @@ The other limitations of LocalStack SSM are: - Only documents using the `aws:runShellScript` plugin are fully supported for execution in Dockerized instances. - Documents using other plugins will fall back to the Moto implementation, which may not function correctly. - Commands returning non-zero codes won't capture standard output or error streams, leaving them empty. -- Shell constructs such as job controls (`&&`, `||`), and redirection (`>`) are not supported. ## API Coverage