An Amazon MWAA DAG starts on schedule, but several tasks remain queued for a long time.
Before retrying blindly, use scheduler and worker evidence to distinguish capacity, dependency, and DAG-processing failures.
Which response should be taken first?
Correlate MWAA scheduler, worker, and task logs in CloudWatch with environment metrics, then choose a targeted capacity or DAG correction.
Detailed explanation
An S3 policy does not change the MWAA scheduler or worker capacity.
An S3 policy does not change the MWAA scheduler or worker capacity.
If capacity or dependencies are the cause, retries increase load and can duplicate downstream work.
If capacity or dependencies are the cause, retries increase load and can duplicate downstream work.
The evidence separates scheduler failures, worker capacity limits, dependency issues, and DAG errors before a retry or scale change.
The evidence separates scheduler failures, worker capacity limits, dependency issues, and DAG errors before a retry or scale change.
Removing retries and evidence makes diagnosis and safe recovery harder.
Removing retries and evidence makes diagnosis and safe recovery harder.
Check official documentation
Compare the following points with the official documentation.
Amazon MWAAのCloudWatch Airflowログ、ログ種別、環境監視の公式説明を確認する。
Official references
What to confirm
MWAAのスケジューラー・ワーカー・タスクログを使った切り分けと、無条件再実行の違いを説明できる。
Key points
- MWAA
- Scheduler logs
- Worker logs
- Queued task
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm the relevant DEA-C01 Skill and current AWS service documentation.
Foundation review
Correlation
Compare logs and metrics from the same time window and DAG run.
Targeted recovery
Change capacity, dependencies, or code only after the cause is identified.