AWS Systems Manager State Manager vs LCFG

AWS Systems Manager State Manager automates keeping managed nodes and other AWS resources in a state that customers define. Its associations specify the configuration to maintain, when to apply it and which resources to target. Targets can be selected by tags, AWS Resource Groups, individual node IDs or all managed nodes in the current Region and account. Associations can run immediately or later and accept most standard cron and rate expressions, but association cron expressions cannot specify months. 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. Association run output can be stored in Amazon S3, and State Manager is supported as an event type and target type in Amazon EventBridge rules. It has no additional charge, although limits may apply. State Manager runs as a cloud service with an agent-based model. AWS Systems Manager follows a shared responsibility model: AWS protects cloud infrastructure, while customer responsibilities depend on the service, data and requirements. Third-party auditors assess Systems Manager under assurance programs including SOC, PCI, FedRAMP and HIPAA.

LCFG is a free, GPL-licensed system for automatically installing and managing configurations across large groups of Unix machines. It targets sites where systems differ and change frequently. Administrators keep source settings on a central server; LCFG compiles them into XML profiles that clients download when changes occur. Client components react to resource changes by generating configuration files and reconfiguring related daemons. A package component aligns installed software with each machine’s profile. New machines can be installed over a network file system after source files are created, using a boot floppy or PXE. LCFG is self-hosted and agent-based, with patch management and HTTP resource transport. Listed supported platforms include Ubuntu 20.04, 22.04, and 24.04; FAQ material also names Fedora Core 3, 5, and 6 and Scientific Linux 5. Solaris support is weaker and un-packaged, Mac OS X is experimental, and the demonstration Windows client lacks real components. Documentation covers configuration, dynamic networking, and build tools.