News for hackers. Stuff that matters.

A comment on SSH Bastion Host Best Practices. Parent comment

Re:SSH Bastion Host Best Practices by rorski on Thursday January 13, 2022 @03:27PM (#29926374)
> A final recommendation: If you use AWS though, consider using Session Manager instead of SSH and drop the bastion host. You can still connect using the SSH command, using proxy command in OpenSSH, but no public IP or bastion host is required.

Yes, this. Also check out https://github.com/rewindio/aws-connect for a convenient wrapper around SSM to make it easier to use (I'm not the author).

[ Parent | on HN ]
Re:SSH Bastion Host Best Practices by debaserab2 on Thursday January 13, 2022 @06:20PM (#29928423)
I wrote something similar after I moved our fleet to SSM because I didn't want yet another CLI app to memorize flags on. It's ruby based and runs in an interactive mode by default. It doesn't cover the whole set of `aws ssm` featureset but focuses just on things that are needed for debugging sort of tasks. Leaving it here incase it's useful to anyone else: https://github.com/ajbdev/ruby-ssm-ops
[ Parent | on HN ]
Re:SSH Bastion Host Best Practices by kubanczyk on Friday January 14, 2022 @05:10AM (#29932638)
Nitpick: the aws-connect quickstart suggests to install it through bpkg. But it turns out that bpkg does not have any "uninstall" or anything similar. I ended up doing just:

    rm ~/.local/bin/aws-connect
[ Parent | on HN ]