A pipeline should start whenever a file lands in S3. What triggers it?
Why B is the answer
An S3 event routed through Amazon EventBridge
Event-driven triggers start work when data arrives.
In detail
- An S3 event routed through EventBridge starts the pipeline.
- A rule can filter by prefix.
Use case
An illustrative scenario, not a real incident.
A partner uploads at random times. An S3 event through EventBridge starts the pipeline on arrival.
See it in different ways
flowchart LR
A["S3 event or schedule"] --> B["Step Functions or MWAA"]
B --> C["Glue job"]
C --> D{"Quality passed?"}
D -->|Yes| E["Load Redshift"]
D -->|No| F["Notify the team"]sequenceDiagram participant S as S3 participant E as EventBridge participant F as Step Functions participant N as SNS S->>E: Object created E->>F: Start the workflow F->>F: Glue job, with retries F-->>N: Alert on failure
sequenceDiagram participant P0 as Amazon S3 participant P1 as EventBridge participant P2 as Pipeline P0->>P1: Object created P1->>P2: Start
Key point: Events start pipelines on arrival.
Why the other options are wrong
- A. An S3 Lifecycle rule
- A Lifecycle rule moves objects.
- C. A cron schedule that polls every hour
- Hourly polling adds delay.
- D. A Glue crawler on a monthly schedule
- A monthly crawler is far too slow.