I'm testing awless in Windows Linux Subsystem (Ubuntu), everything seems to be fine, until I try to use it to ssh into an instance.
➜ ~ awless ssh Bastion -i key.pem -e
[verbose] awless v0.1.11 - loading AWS session with profile 'uat' and region 'eu-west-1'
[extra] loading credentials from '/home/xxxxxx/.awless/cache/credentials/profile.json'
[extra] dialed xxx.xxx.xxx.83:22 successfully with user ubuntu
[info] Login as 'ubuntu' on 'xxx.xxx.xxx.83'; client '/usr/bin/ssh'
[extra] running locally [/usr/bin/ssh -i key.pem ubuntu@xxx.xxx.xxx.83]
[error] cannot allocate memory
Same thing happens if I try to ssh to a private instance using --through
➜ ~ uname -a
Linux DESKTOP-xxxxXXX 4.4.0-17134-Microsoft #137-Microsoft Thu Jun 14 18:46:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
➜ ~ free
total used free shared buff/cache available
Mem: 33333844 15285008 17812360 17720 236476 17907980
Swap: 100663296 0 100663296
Anything I can do to make it work? It would really help us in our team if we can use it to ssh to a private instance without caring about IP addresses.
Thanks.
I'm testing awless in Windows Linux Subsystem (Ubuntu), everything seems to be fine, until I try to use it to ssh into an instance.
Same thing happens if I try to ssh to a private instance using --through
Anything I can do to make it work? It would really help us in our team if we can use it to ssh to a private instance without caring about IP addresses. Thanks.