aws ssm start-session no respnose for M1 chip

[johnluan]

I have two mac one is intel chip and one is M1 chip. When I run aws ssm start-session --profile prod --target XXX

Client side The M1 chip one has no any response, it didn't start session.

(base) MacBook-Pro ~ % aws ssm start-session --profile prod --target i-xxx
(base) MacBook-Pro ~ %

If I add --debug, the two laptop have almost identital info, beside the M1 chip has no "Starting session"

Server side If I log into the ec2 instance, for /var/log/amazon/ssm/amazon-ssm-agent.log. both laptops trigger the same log info. It is clearly connected. But client side didn't start session [DataBackend] [pluginName=Standard_Stream] Starting websocket pinger [DataBackend] [pluginName=Standard_Stream] Starting websocket listener [DataBackend] [pluginName=Standard_Stream] Skipping handshake. [DataBackend] [pluginName=Standard_Stream] Starting command executor [DataBackend] [pluginName=Standard_Stream] ssm-user already exists. [DataBackend] [pluginName=Standard_Stream] Plugin Standard_Stream started

AWSCLI version aws-cli/2.9.4 Python/3.11.0 Darwin/21.3.0 source/arm64 prompt/off

Please help, I have no way to figure out what is the reason, I need this to access to prod server

[YujiaozhAws]

Hi johnluan@,

Thanks for reaching out. We don't support Session Manager Plugin on MacOs M1 ARM. Our team will look into this ask, and update when it is ready.

Thanks.

[mrostamii]

Hi, any news on this? I have M3 Pro chip, and it hangs when trying to start a session:

aws ssm start-session --target i-<instanceId>

Starting session with SessionId: <user>-<id>
# hangs here

Also, adding --no-cli-pager doesn't work.

[iouri-forusall]

Works on my m3. First run took a long time and might have hung up as reported, but after that it was acting and working as expected. aws-cli/2.16.5 Python/3.11.9 Darwin/23.4.0 source/arm64