AWS Systems Manager State Manager

AWS Systems Manager State Manager helps AWS customers keep managed nodes and other AWS resources in a defined configuration. It is best suited to teams governing AWS fleets and reducing configuration drift. Its strongest case is scheduled, repeatable maintenance without an additional State Manager charge; AWS-scoped targeting and a cron limitation make it a narrower fit for broader environments.

Overview

State Manager uses associations to specify the desired state of a resource, when to apply it, and which resources to target. That makes it a practical choice for ongoing configuration management within AWS, rather than a general-purpose way to manage infrastructure across unrelated environments.

Associations can run immediately or after a delay and accept most standard cron and rate expressions. The exception matters for calendar-driven work: cron expressions for associations cannot specify months. Targets can be selected by tags, AWS Resource Groups, individual node IDs, or all managed nodes in the current Region and account. Those options suit routine fleet-wide or group-level changes, but the Region-and-account boundary may complicate work spanning a wider estate.

Key features

On Linux, macOS, and Windows Server managed nodes, State Manager can bootstrap software, schedule agent updates, configure network settings, join nodes to a Microsoft Active Directory domain, and run scripts. These capabilities cover common setup and upkeep tasks, giving teams a way to apply consistent configurations instead of handling each node separately.

State Manager supports drift detection, patch management, policy as code, and compliance reporting. Associations can store run output in Amazon S3, and State Manager can serve as an event type and target type in Amazon EventBridge rules. Together, these functions suit AWS operations teams that want configuration work connected to their existing AWS workflows; they do not remove the need to account for the service's targeting and scheduling boundaries.

AWS follows a shared responsibility model: AWS protects the cloud infrastructure, while customer responsibilities vary with the service, data, and requirements. Systems Manager is assessed by third-party auditors under assurance programs including SOC, PCI, FedRAMP, and HIPAA. Those programs provide useful assurance context, but customers still need to understand and meet their own responsibilities.

Pricing

AWS Systems Manager State Manager — free. The free plan has no additional charge, though limits may apply. There are no paid tiers to weigh against the free offering in this plan structure. That makes State Manager an economical fit for AWS customers who can work within its limits; teams should still account for those limits when planning larger-scale use.

Platforms

State Manager is cloud-based and agent-based. Its supported managed-node platforms are Linux, macOS on Amazon EC2, and Windows Server. While the platform details also include web, the managed-node tasks described here are for those operating systems; macOS support is specifically tied to Amazon EC2.

Who it's for

State Manager is the right choice for AWS customers who want to reduce configuration drift and govern AWS resources through repeatable associations. It is especially relevant when teams need to schedule maintenance or apply scripts and standard settings across managed nodes. Look elsewhere if your environment requires targeting beyond the current AWS Region and account or calendar schedules that depend on selecting specific months.

Pros and cons

• Pros: No additional charge makes routine configuration maintenance accessible without a State Manager fee.
• Pros: Associations combine desired state, timing, and targeting, with options from individual node IDs to tags, Resource Groups, or all managed nodes in a Region and account.
• Pros: Node-management tasks cover software bootstrap, agent updates, network settings, directory joining, and scripts across supported systems.
• Cons: Association cron expressions cannot specify months, limiting some calendar-based schedules.
• Cons: Targeting all managed nodes is limited to the current Region and account, which is restrictive for broader coordination.
• Cons: Limits may apply despite the lack of an additional charge.

Alternatives

For teams comparing configuration-management options, the Configuration Management Tools, IT Operations Management Software, IT Configuration Management Software, and IT Automation Software lists provide broader starting points.

• CFEngine offers a free Community Edition under the GNU GPL with Linux support and community support; it also has a freemium model and free trial.
• Rudder is a freemium option with a free plan and free trial; its source code can be downloaded and modified under its open source licenses.
• Salt offers a free Salt Open Source plan under the Apache 2.0 license.
• config.XO has a free forever plan capped at one workspace, one admin user, one cloud connection, one hypervisor, three managed systems, and one API key.
• Google Cloud VM Manager may suit teams managing Google Cloud VMs: its plan is billed at $0.003 per hour per VM with an active OS Config agent after the free tier, per VM-hour, with a 100-VM monthly allowance per Cloud Billing account.
• OpenVox is a free, community-maintained option for agent/server or standalone use.
• pyinfra is a free, MIT-licensed option requiring Python 3.10 or later.
• Uyuni is free, open-source configuration and infrastructure management; hardware requirements depend on deployment and channel requirements.

Verdict

Choose AWS Systems Manager State Manager if you are an AWS customer seeking no-additional-charge, scheduled configuration management for supported managed nodes and resources. Its associations and node-maintenance tasks make it a focused fit for reducing drift within AWS. Choose another approach if you need month-specific cron scheduling, targeting beyond the current Region and account, or an environment outside its AWS-centered scope.