aws ssm start-session no respnose for M1 chip
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
Research direction
Start by reproducing `aws ssm start-session --profile prod --target XXX` on the arm64 M1 client with `--debug`, then compare its output with the Intel client. Check the client behavior against the EC2 instance's `/var/log/amazon/ssm/amazon-ssm-agent.log`; done means the M1 client starts and maintains the session with the same target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100