Re:AWS Secrets Manager – Store, Distribute, and Rotate Crede...
by cassianoleal on Wednesday April 04, 2018 @07:41PM
(#16760397)
Wait, you keep private SSH keys on bastion hosts?
It's much better practice to use the bastion as a proxy to the other hosts. This is easily achieved using the ProxyCommand option of OpenSSH.
No agent forwarding, no secrets kept in random hosts.
Re:AWS Secrets Manager – Store, Distribute, and Rotate Crede...
by JoachimSchipper on Thursday April 05, 2018 @01:15AM
(#16761985)
No, keeping SSH keys on bastion hosts was the silliest reasonable thing I could think of.
Re:AWS Secrets Manager – Store, Distribute, and Rotate Crede...
by scrollaway on Wednesday April 04, 2018 @09:23PM
(#16760963)
Do you know a good guide with standard practices for setting up and securing bastion hosts (preferably on aws)?
Re:AWS Secrets Manager – Store, Distribute, and Rotate Crede...
by toomuchtodo on Wednesday April 04, 2018 @11:54PM
(#16761626)
If you don’t require interactive sessions, consider using AWS SSM run command [1] instead. You install the agent on the instances, with commands sent from the client through the AWS control plane (with IAM and SSM documents for access control and CloudTrail logs of all commands issued).
I’m currently deploying it in an enterprise for ~5k users, and it works surprisingly well for providing the ability to run arbitrary commands on instances without ssh access.
[1] https://docs.aws.amazon.com/systems-manager/latest/userguide...
("Well-secured workstation" is arguably an oxymoron, of course...)