You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cmd.exe: aws ssm start-session: Cannot enter "$" or "@" w/Norwegian keyboard layout, nor paste #9815
I have a Norwegian keyboard, and when I press AltGr+4 for $, or AltGr+2 for @ in a CLI SSM session then nothing happens. $ and @ works everywhere else.
Likewise, if I paste anything containing $ or @ then the special characters are ignored.
If I change keyboard layout to US, then I can press Shift+4 and Shift+2 for $ and @ respectively. But I still cannot paste.
Regression Issue
Select this option if this issue appears to be a regression.
Expected Behavior
If I type or paste a string with "$", I expect "$" to be included in the CLI SSM session.
Current Behavior
If I type or paste a string with "$", nothing happens in the CLI SSM session.
Reproduction Steps
Have Windows 11 with Norwegian keyboard layout
Have EC2 instance with recent Amazon Linux (mine has Linux/6.1.127-135.201.amzn2023.x86_64)
Connect to the EC2 instance using aws ssm start-session ...
Type $ or @, or paste a string containing either or both
Possible Solution
No response
Additional Information/Context
Using aws-cli/2.27.35 Python/3.13.3 Windows/11 exe/AMD64
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Activity
adev-code commentedon Oct 29, 2025
Hello @andersnm, thanks for reaching out. I have reached out to the SSM in this regard. I will update as soon as there are any updates from the team.
Internal Ref: P328152902
adev-code commentedon May 18, 2026
The service team has mentioned that this has been released: https://github.com/aws/session-manager-plugin/releases/tag/1.2.792.0
github-actions commentedon May 18, 2026
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.