Question #1536
A company wants to send all AWS Systems Manager Run Command logs to an Amazon S3 bucket for archival purposes.
Which solution will meet this requirement with the MOST operational efficiency?
Enable S3 logging in the Systems Manager console. Choose an S3 bucket to send the Run Command logs to.
Install the Amazon CloudWatch agent. Push all logs to a CloudWatch log group. Export the logs to an S3 bucket from the group for archival purposes.
Create a Systems Manager document to upload all Run Command logs to a central S3 bucket. Use Amazon EventBridge to run the document against all instances daily.
Install an Amazon CloudWatch agent. Push all logs to a CloudWatch log group. Create a CloudWatch logs subscription that pushes any incoming log events to an Amazon Kinesis Data Firehose delivery stream. Set Amazon S3 as the destination.
Explanation
Answer A is correct because AWS Systems Manager provides a built-in feature to send Run Command logs directly to an S3 bucket. Enabling this requires minimal effort: users only need to configure the logging option in the SSM console and specify the target S3 bucket. This approach eliminates the need for additional components like agents (Options B, D), custom documents (Option C), or integrations with CloudWatch/Kinesis (Options B, D), making it the most operationally efficient solution.
Other options are less efficient:
- Option B requires installing the CloudWatch agent and manually exporting logs from CloudWatch to S3, adding complexity.
- Option C involves creating a custom SSM document and scheduling it via EventBridge, which introduces maintenance overhead.
- Option D uses CloudWatch, Kinesis Data Firehose, and an agent, increasing operational complexity.
Key Points:
- SSM Run Command natively supports S3 logging.
- Direct S3 integration minimizes setup and maintenance.
- Avoid unnecessary services/agents for operational efficiency.
Answer
The correct answer is: A