Amazon-ssm-agent: Support fargate/SSM Sessions

Created on 13 Nov 2018  ·  11Comments  ·  Source: aws/amazon-ssm-agent

My use case is to allow me to easily SSH to instances inside of my private VPC using SSM Sessions. The biggest hurdle to getting this running is a different metadata url, as well as certian metadata items not being available in fargate, like InstanceId.

I've attached a dockerfile to make it easy to test.

Most helpful comment

@holyjak Yup, USD$5 a pop, per month ☹️ Hopefully our friends at @aws can bake in native Fargate support sometime soon...

Chances are, until then, I'll be using this pretty heavily. I think once the basic functionality and error handling are sorted, I'll bake the SNS/Lambda cleanup and service registration into a CDK script and then dump this into a proper GitHub repo.

All 11 comments

Hi @jjshoe,

Thank you for the feedback. We'll look into this issue.

Another use case is to have a lite version of cloud shell.

Why has this been closed?

Yep curious as well - @hiimtu why is this closed?
Especially with ssm agent now supporting port forwarding could be useful for total serverless ephemeral port forwarding

Didn't mean to close. Apologies!

My use case for ssm access on fargate is to run chaos experiments: https://github.com/adhorn/chaos-ssm-documents

Here is a bit of a janky/expensive workaround I just started using... It _seems_ to be doing the trick though: https://gist.github.com/andrewodri/1403c0e28503051e26b24428f1ae49b9

Basically you're just registering your Fargate instance as if it were an on-prem server in a hybrid environment.

Nice!

You pay for each registered instance, right? So implementing removal of
unused Registrations will be quite important, since you get a new one upon
each deployment or scale down.

On Sat, 22 Feb 2020, 08:55 Andrew Odri, notifications@github.com wrote:

Here is a bit of a janky/expensive workaround I just started using... It
seems to be doing the trick though:
https://gist.github.com/andrewodri/1403c0e28503051e26b24428f1ae49b9

Basically you're just registering your Fargate instance as if it were an
on-prem server in a hybrid environment.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/amazon-ssm-agent/issues/138?email_source=notifications&email_token=AAEYSPRSELTIZXJTDF6K3ITREDK5NA5CNFSM4GDKL3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMUZ4VY#issuecomment-589930071,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYSPTT2KINBAJFTKADU4LREDK5NANCNFSM4GDKL3JA
.

@holyjak Yup, USD$5 a pop, per month ☹️ Hopefully our friends at @aws can bake in native Fargate support sometime soon...

Chances are, until then, I'll be using this pretty heavily. I think once the basic functionality and error handling are sorted, I'll bake the SNS/Lambda cleanup and service registration into a CDK script and then dump this into a proper GitHub repo.

Is this on the roadmap? This would be a huge factor in my advocacy to switch off of kubernetes and onto a pure aws stack.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

TravellingGuy picture TravellingGuy  ·  6Comments

wayneworkman picture wayneworkman  ·  5Comments

dwilches picture dwilches  ·  4Comments

heydonovan picture heydonovan  ·  3Comments

guizmaii picture guizmaii  ·  3Comments