AWS Systems Manager State Manager vs Google Cloud Observability

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.

Google Cloud Observability has no write-up on Specifiction yet; its figures are above.