Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Commit f643c5a

Browse files
authored
Clarify limitations of SSM SendCommand action (#1719)
1 parent 4f20f79 commit f643c5a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

content/en/user-guide/aws/ssm/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ You can copy the `InstanceId` value and use it in the following commands.
6969
7070
### Send command using SSM
7171
72-
You can use the [`SendCommand`](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_SendCommand.html) API to send commands to the EC2 instance.
72+
You can use the [`SendCommand`](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_SendCommand.html) API to send a command to the EC2 instance.
7373
The following command sends a `cat lsb-release` command in the `/etc` directory to the EC2 instance.
7474
7575
{{< command >}}
@@ -149,5 +149,6 @@ The following table highlights some differences between LocalStack SSM and AWS S
149149
The other limitations of LocalStack SSM are:
150150
151151
- Dockerized instances only support `AWS-RunShellScript` commands.
152+
- [`SendCommand`](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_SendCommand.html) only runs 1 command per invocation and will ignore multiple commands passed as an array, starting from the 2nd one.
152153
- Commands returning non-zero codes won't capture standard output or error streams, leaving them empty.
153154
- Shell constructs such as job controls (`&&`, `||`), and redirection (`>`) are not supported.

0 commit comments

Comments
 (0)