A CloudOps team manages 300 running EC2 instances that are already Systems Manager managed nodes. The team must start collecting memory and disk-space metrics. Any later change to the collected metrics must be made in one place and reach every running instance without replacing or rebooting it. Which approach meets these requirements with the LEAST operational overhead?
Choose one.
The CloudWatch agent reads a JSON configuration. Storing that configuration in Systems Manager Parameter Store and applying it with Systems Manager (AWS-ConfigureAWSPackage to install, AmazonCloudWatch-ManageAgent to configure) gives a whole fleet one consistent, centrally changed configuration.
Three constraints decide it: the instances are already running, they must not be replaced or rebooted, and later changes must be made in one place. Parameter Store plus the AmazonCloudWatch-ManageAgent document meets all three; re-running the command after editing the parameter updates every node in place. AWS-ConfigureAWSPackage is the near-twin: it installs the agent but does not configure it. A configuration file read at boot and launch-template user data only take effect when an instance starts.
- Note that in-guest metrics (memory, disk space) need the CloudWatch agent with a configuration that lists them.
- Note the constraints: running instances, no replacement or reboot, one place for later changes.
- Eliminate boot-time mechanisms (user data, a file downloaded at startup) because running instances never read them.
- Eliminate AWS-ConfigureAWSPackage on its own because it installs the agent but applies no configuration.
- Choose Parameter Store for the configuration and AmazonCloudWatch-ManageAgent to apply it.
Exam tip: Fleet-wide CloudWatch agent: configuration in Parameter Store, installed and applied with Systems Manager.
CloudWatch Metrics, Alarms, and Log Filters for SOA-C03 — the lesson that teaches this.