A daily data pipeline runs for several hours and must retain each state for audit.
External approval waits and post-failure inspection are required.
Which workflow type is most appropriate?
Choose Step Functions Standard Workflows for long runs, execution history, and external waiting.
Detailed explanation
Notifications do not retain the state of multiple long-running tasks.
Notifications do not retain the state of multiple long-running tasks.
Recursion cannot safely provide workflow history, stopping, cost control, or durable waiting.
Recursion cannot safely provide workflow history, stopping, cost control, or durable waiting.
Standard is designed for long-running, auditable workflows with execution history and external waits.
Standard is designed for long-running, auditable workflows with execution history and external waits.
Express suits high-volume short runs; long history and waiting requirements need other controls.
Express suits high-volume short runs; long history and waiting requirements need other controls.
Check official documentation
Compare the following points with the official documentation.
Step Functions Standard・Express Workflowsの実行時間、履歴、料金、実行モデルを確認する。
What to confirm
処理量だけでなく、履歴・待機・実行モデルを基準に方式を選べる。
Key points
- Standard Workflows
- Express Workflows
- Execution history
- Long-running
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Execution model
Duration, history, delivery semantics, and cost all influence the workflow type.
Observability
History, logs, traces, and replay behavior should meet the audit requirement.