Are they basically trying to emulate GCP’s OS Login ( https://cloud.google.com/compute/docs/instances/managing-ins... ) feature here? We’ve been using that for a while, and it’s been a big relief.
AWS Session Manager: less infrastructure, more features
11–20 of 49 posts
Re: AWS Session Manager: less infrastructure, more features
#12This is awesome! How can I install the the agent if I'm not using Amazon Linux?
Re: AWS Session Manager: less infrastructure, more features
#13Would be interesting to lock down the session manager agent (if possible) so that the only way to privileged access is through sudo-like priv esc that uses 2fa.
Re: AWS Session Manager: less infrastructure, more features
#14IAM is easy to mess up. Would be interesting to lock down the session manager agent (if possible) so that the only way to privileged access is through sudo-like priv esc that uses 2fa.
For federation you need to rely on the config in whatever your identity provider is, like Okta.
Re: AWS Session Manager: less infrastructure, more features
#15Are they basically trying to emulate GCP’s OS Login ( https://cloud.google.com/compute/docs/instances/managing-ins... ) feature here? We’ve been using that for a while, and it’s been a big relief.
Re: AWS Session Manager: less infrastructure, more features
#16I'd love to learn how you're using Session Manager or what other features/integrations you'd like to see us explore. Also if the terraform module packaging is useful. There are additional Session Manager features like port forwarding that I plan to write about soon.
Can you write one about port forwarding? Specifically, I would like to understand how various web interfaces on EMR cluster can be accessed through Sessions Manager. (Ganglia, Spark history server, etc.)
"Tunnel created using SSM only allows single connection to destination port" - https://forums.aws.amazon.com/thread.jspa?threadID=314882&ts...
This has been sitting open in the support forums unanswered for over two months :/
Re: AWS Session Manager: less infrastructure, more features
#17Are they basically trying to emulate GCP’s OS Login ( https://cloud.google.com/compute/docs/instances/managing-ins... ) feature here? We’ve been using that for a while, and it’s been a big relief.
os login is probably a little closer to ec2 instance connect because you still need ssh inbound access right? whereas aws provides a bastion here
[1] https://cloud.google.com/compute/docs/instances/connecting-a...
Re: AWS Session Manager: less infrastructure, more features
#18Are they basically trying to emulate GCP’s OS Login ( https://cloud.google.com/compute/docs/instances/managing-ins... ) feature here? We’ve been using that for a while, and it’s been a big relief.
os login is probably a little closer to ec2 instance connect because you still need ssh inbound access right? whereas aws provides a bastion here
Re: AWS Session Manager: less infrastructure, more features
#19This is awesome! How can I install the the agent if I'm not using Amazon Linux?
Re: AWS Session Manager: less infrastructure, more features
#20Earlier quoted context omitted.
os login is probably a little closer to ec2 instance connect because you still need ssh inbound access right? whereas aws provides a bastion here
You're right in a sense, but there's no aws-managed bastion. Session manager communicates with your instance via an outbound-created websocket connection. Inputs and outputs are piped through it.