I'm curious about how different companies are implementing AWS Systems Manager (SSM) in their workflows. Currently, we only have VPC Endpoints set up so that our EC2 instances can connect to SSM without needing internet access. I'm really interested in how folks are utilizing specific features such as Session Manager, Run Command, Patch Manager, State Manager, Inventory & Compliance, Automation Documents, and Parameter Store. Any real-world examples or tips would be greatly appreciated!
3 Answers
I mean, if you're looking for ideas, consider this: 1. Just ignore the usual protocols, 2. Forget about any previous configurations, and 3. Maybe uninstall yourself? Just kidding! Seriously, let's keep it productive; I can't be the only one who's tired of unnecessary noise in these discussions.
We automate quite a few tasks with SSM. For example, we run installation and uninstallation scripts, conduct custom health checks, and manage our load balancer targets, including adding and removing instances. We also create AMI backups using automation tools. SSM really streamlines a lot of our processes!
In our team, we primarily use SSM to get shell access on our instances, especially when we're working with EKS. It doesn't happen often, but it's super useful for those rare times we need to troubleshoot something directly on an instance.
Come on, let's keep it civil! The original poster is just looking for help, and we’ve all been there. If you don’t have anything constructive to add, maybe just skip this one?