AWS Systems Manager

What differentiates AWS Systems Manager from other similar products?

Deep native integration with AWS IAM and CloudTrail out of the box. Unlike Ansible or custom Bastions, Session Manager provides secure shell access without opening inbound ports 22/3389 or managing SSH key lifecycles.

What is your favorite aspect of this product?

Parameter Store combined with KMS encryption. It provides a simple, cost-effective way to manage configuration data and secrets across CI/CD pipelines and ECS/EKS container deployments.

What do you dislike most about this product?

The AWS console UI for Systems Manager is heavily bloated. Navigating between Fleet Manager, Automation, State Manager, and Patch Manager feels clunky, and debugging failed SSM Automation executions can be tedious due to buried logs.

What recommendations would you give to someone considering this product?

Ensure the SSM Agent is baked directly into your base AMI or launch template configurations day one. Also, configure S3/CloudWatch logging for Session Manager immediately so you have immutable audit trails for shell access.

What differentiates AWS Systems Manager from other similar products?

As an Information Technology Manager, I believe AWS Systems Manager stands out because it provides a unified way to manage, monitor and automate operations across AWS resources from a single console. Unlike many traditional systems management tools that require separate solutions for patching, configuration management, automation, and inventory tracking, AWS Systems Manager brings these capabilities together in a tightly integrated platform. Its native integration with AWS services makes it easier to manage large-scale cloud environments while reducing operational overhead.

What is your favorite aspect of this product?

My favourite aspect of AWS Manager is how seamlessly it enables automation at scale without adding operational complexity. According to my point of view, I really value being able to manage patching, configuration changes, and routine maintenance across a large number of instances from a single, centralized tool. The fact that it integrates natively with the AWS ecosystem means I don’t have to stitch together multiple tools or worry about maintaining separate management infrastructure. It makes day-to-day operations more efficient while also improving consistency and compliance across environments.

What do you dislike most about this product?

What I dislike most about AWS Systems Manager is that it can feel a bit overwhelming and fragmented when we first start using it. While it’s powerful, the different components like Automation, Patch Manager, Session Manager, and Parameter Store each have their own setup requirements and learning curve. For teams that are not already deeply embedded in AWS, it can take time to understand how everything fits together and to configure it properly. I also find that its full value is really realized only in a well-architected AWS environment, which can limit flexibility if we are working in hybrid or multi-cloud setups.

What recommendations would you give to someone considering this product?

If I were recommending AWS Systems Manager, I would say it’s a strong choice if our organization is already invested in AWS and we want to simplify operations at scale. It works best we are looking to centralize patching, automation, and instance management without introducing additional third-party tools. That said, I would suggest starting with a clear use case like patch management or secure remote access rather than trying to adopt everything at once. The platform is powerful, but it has a learning curve, so gradual implementation with well-defined processes tends to deliver to best results.

What differentiates AWS Systems Manager from other similar products?

It's cost efficiency as most of System Manager features are available at no additional cost and also it's full native AWS ecosystem integration

What is your favorite aspect of this product?

I normally use Ansible to SSH into my instance via port 22. I can't do this on prod that's when i figured out AWS SSM where i do agentless access to my prod instances without requiring SSH and closing port 22 and not needing bastion host

What do you dislike most about this product?

I do face some performance issues when executing commands which sometimes impacts my workflows

What recommendations would you give to someone considering this product?

Don't try to implement everything at once. Start with Session Manager for secure instance access and Parameter Store for secrets management because these provide immediate value with minimal difficulties. Once comfortable, gradually add Patch Manager, Automation, and other advanced capabilities