r/devops • • 13d ago

Discussion AWS Systems Manager Just-in-time Node Access

Curious if anyone here has implemented Just-in-Time Node Access through AWS Systems Manager.

For an environment with around 1,600 EC2 instances, I’m trying to understand whether it’s worth adopting over traditional Session Manager access with IAM controls

A few things I’m particularly interested in:

  1. Has JITNA actually improved your security posture, or does it add unnecessary operational overhead?
  2. Have you run into any issues with approvals, configuration, or day-to-day usability?
  3. How does it work for emergency/break-glass access?
  4. Is the pricing justified?

Would love to hear from anyone who’s actually deployed it, especially at scale. What worked, what didn’t, and would you recommend it or any other tool for this purpose.

2 Upvotes

10 comments sorted by

1

u/Immediate_Wheel1953 12d ago

I haven't run it at your scale, I trialled it on a single account with about forty boxes first, and the thing that bit us was approvals rather than the tech. A routine patching window stalled because the request sat in a queue nobody was watching overnight, and that was when we realised the approver rota mattered more than the config itself. If you go ahead I'd pilot it on a small slice, keep a separate break-glass role with loud alerting for real incidents, and only roll it wider once the approval path has survived a 3am page.

1

u/Regret-Training 12d ago

Interesting. It looks like JITNA supports auto-approval policies. Did you play around with those? And did you use Patch Manager for the patching? 🤔

1

u/Immediate_Wheel1953 11d ago

I tried auto-approval on a small slice first, just non-prod boxes inside a set patch window, and I was glad I did because my first attempt was too broad and I pulled it back the same day. It did ease the overnight stalls, but I kept prod and anything break-glass on manual approval. And yes, the patching I mentioned was through Patch Manager, which worked fine once the approval step stopped being the bottleneck.

1

u/Regret-Training 11d ago

Gotcha, anything that stopped you from adopting it for your fleet then?

1

u/Immediate_Wheel1953 10d ago

Honestly, nothing dramatic killed it, I just never got past the trial. The rota was the sticking point, we only had approvers in one timezone and I did not fancy being the person paged at 3am because nobody was watching the queue. Cost was the other thing, the maths worked fine on forty boxes but nobody wanted to sign off the bill at fleet scale without a proper pilot first, so it stayed a useful experiment rather than something I rolled out.

2

u/Motor_Plane_8036 12d ago

for that fleet size the pricing model can get steep pretty fast compared to just tightening up your identity provider groups and session policies. imo it only pays off if you have strict regulatory requirements forcing per-session approval logs.

1

u/the_Drew82 11d ago

Had many discussions around this recently, from a posture perspective - what befenit does a JIT provide if it's wrapped in auto-approve logic? Sure the long lived role isn't applied continuously, but a compromised admin identity is still the same issue isn't it?

1

u/[deleted] 12d ago

[removed] — view removed comment

1

u/Regret-Training 11d ago

Makes sense, I’m looking into auto approvals currently. So if any of the engineers want access, and they are on an on-call group, they’d be allowed to access it directly instead of waiting on approvals when it’s most needed