search

aws / amazon-ssm-agent

An agent to enable remote management of your EC2 instances, on-premises servers, or virtual machines (VMs).
https://aws.amazon.com/systems-manager/
Apache License 2.0
1.05k stars 323 forks source link

CTRL+O in nano editor doesn't work when I connect to the managed nodes using local SSM plugin on macOs #510

Open Hamed527 opened 1 year ago

Hamed527 commented 1 year ago

Hello there!

CTRL+O in the nano editor doesn't work when I connect to the managed nodes using the local SSM plugin on macOS. Any idea and helps would be appreciated. My colleagues and I are struggling with this issue and I suppose there should be more signal issues there.

Thanks.

Hamed!

justinmk3 commented 1 year ago

what steps did you take exactly?

Related:

Hamed527 commented 1 year ago

Thank you for the reply. I have already checked and tried this post. So this workaround didn't work for me:

Run stty dsusp undef on your host. Start a shell session aws ssm start-session --target i-00112233445566778 Press Ctrl-y to paste from the kill ring (which is empty, so nothing happens).

So I ran stty dsusp undef on my local mac. Then I started the session by aws ssm start-session --target [instance-id] and then when connected to the node as ssm-user , I pressed Ctrl+y. But no success.

If you mean the exact steps to connect to the node using the session manager plugin, I guess I did it right. As everything seems normal. Thanks again for your help.

Hamed527 commented 1 year ago

what steps did you take exactly?

Related:

Thank you for the reply. I have already checked and tried this post. So this workaround didn't work for me:

Run stty dsusp undef on your host. Start a shell session aws ssm start-session --target i-00112233445566778 Press Ctrl-y to paste from the kill ring (which is empty, so nothing happens).

So I ran stty dsusp undef on my local mac. Then I started the session by aws ssm start-session --target [instance-id] and then when connected to the node as ssm-user , I pressed Ctrl+y. But no success.

If you mean the exact steps to connect to the node using the session manager plugin, I guess I did it right. As everything seems normal. Thanks again for your help.

mikewyer commented 1 year ago

This could well be a duplicate of https://github.com/aws/amazon-ssm-agent/issues/174

yuting-fan commented 1 year ago

Hi, currently Session Manager plugin processes a subset of control signals https://github.com/aws/session-manager-plugin/blob/mainline/src/sessionmanagerplugin/session/sessionutil/control_signals_unix.go#L25-L33. I have captured your request in our input queue. We will update once we support new control signals as requested.

Cheers, Yuting