You run the Apache Airflow workflows you already have. Which service manages them?
Why A is the answer
Amazon Managed Workflows for Apache Airflow
MWAA runs Airflow as a managed service.
In detail
- Amazon MWAA runs your existing Airflow workflows.
- Your DAGs change little.
Use case
An illustrative scenario, not a real incident.
A team has many Airflow DAGs and moves them to MWAA, so that AWS manages Airflow itself.
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
flowchart TD
Q{"Do you already use Airflow?"}
Q -->|"Yes"| A0["Amazon MWAA"]
Q -->|"No, starting fresh"| A1["Consider Step Functions"]Key point: MWAA runs Airflow as a service.
Why the other options are wrong
- B. Amazon EventBridge Scheduler, with one rule per task
- A scheduler does not run Airflow DAGs.
- C. AWS Batch, with a job queue for each directed graph
- AWS Batch runs batch jobs.
- D. AWS Glue Data Catalog, with a table for each workflow
- A catalog holds metadata.