A company regularly receives new training data from the vendor of an ML model. The vendor delivers cleaned and prepared data to the company's Amazon…

The most efficient solution with the least operational effort is to use Amazon EventBridge. Amazon S3 natively emits events for actions like object creation. An EventBridge rule can be configured to listen for the specific s3:ObjectCreated: event in the designated S3 bucket. Amazon SageMaker Pipelines can be set as a direct target for an EventBridge rule. This creates a direct, serverless, event-driven integration that requires no custom code or intermediate services, minimizing both setup and ongoing operational management.

A: S3 Lifecycle rules are for managing object storage classes and expiration (e.g., moving data to Glacier), not for initiating compute workflows like a SageMaker pipeline.

B: While a Lambda function can trigger the pipeline, it requires writing, deploying, and maintaining custom code, which represents more operational effort than a direct EventBridge integration.

D: Amazon MWAA is a powerful but complex workflow orchestration service. Setting it up for a simple event-based trigger is significant overkill and involves the highest operational effort.

1. Amazon SageMaker Developer Guide: Describes how to automate pipeline execution using events. It explicitly states

"You can start a pipeline execution based on... an event by using Amazon EventBridge... For example

you can set up a rule in EventBridge to start a pipeline run when new data is uploaded to an Amazon S3 bucket."

Source: AWS SageMaker Developer Guide

"Starting a Pipeline Execution".

2. Amazon EventBridge User Guide: Details how S3 events are delivered to EventBridge and how to create rules that match these events. It lists "SageMaker Pipeline" as a valid target that can be invoked directly.

Source: AWS EventBridge User Guide

"Events from AWS services" and "Amazon EventBridge targets".

3. Amazon S3 User Guide: Explains the purpose of S3 Lifecycle configurations

which is to "manage your objects so that they are stored cost effectively throughout their lifecycle." This confirms it is not a tool for triggering compute jobs.

Source: AWS S3 User Guide

"Managing your storage lifecycle".