A pipeline definition must be updated while executions already in progress finish with the old definition.
Only new executions should use a tested version.
Which operational approach is most appropriate?
Use Step Functions versions and aliases to keep running executions stable and switch new executions after validation.
Detailed explanation
IAM policy versions control permissions, not Step Functions state-machine definitions.
IAM policy versions control permissions, not Step Functions state-machine definitions.
Changing the definition in place harms reproducibility and can conflict with in-flight state.
Changing the definition in place harms reproducibility and can conflict with in-flight state.
A file-name change does not safely change the definition referenced by the execution API.
A file-name change does not safely change the definition referenced by the execution API.
The alias can move new executions to a tested definition while existing executions retain their version.
The alias can move new executions to a tested definition while existing executions retain their version.
Check official documentation
Compare the following points with the official documentation.
Step Functions state machine versions、aliases、deploymentの公式説明を確認する。
What to confirm
ワークフロー定義の版管理とIAMポリシー版管理を区別できる。
Key points
- State machine version
- Alias
- Deployment
- Rollback
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Definition immutability
Fixing the execution's definition preserves reproducibility during a deployment.
Safe rollout
Validate a new version, switch the alias, and keep a rollback path with execution evidence.