A company needs a serverless solution that collects Amazon EC2 Auto Scaling events across all applications in an AWS account and stores the status data in Amazon S3 for near-real-time dashboard updates. The solution must not affect the speed of EC2 instance launches. How should the company move the data to Amazon S3 to meet these requirements?

The correct solution uses an Amazon CloudWatch metric stream to capture EC2 Auto Scaling events. CloudWatch is the native service for monitoring AWS resources and can stream logs and metrics, including Auto Scaling events, to Kinesis Data Firehose. Kinesis Data Firehose is a fully managed service that reliably loads streaming data into data lakes, data stores, and analytics services, including Amazon S3, making it ideal for near-real-time dashboard updates without impacting EC2 instance launches. Using an Amazon EMR cluster is overkill and not serverless for this task. Creating an Amazon EventBridge rule to invoke a Lambda function on a schedule would not capture events in near real-time as they occur; it would only poll periodically. Using a bootstrap script with Kinesis Agent on EC2 instances is for collecting instance-specific logs or metrics, not for capturing Auto Scaling service events, and it would also add overhead to instance launch times, violating the requirement.