You can use Step Functions to manage continuous deployments of your workflows through state machine versions and aliases. A version is a numbered, immutable snapshot of a state machine that you can run. An alias is a pointer for up to two versions of a state machine.
You can maintain multiple versions of your state machines and manage their deployment in your production workflow. With aliases, you can route traffic between different workflow versions and gradually deploy those workflows to the production environment.
Additionally, you can start state machine executions using a version or an alias. If you don't use a version or alias when you start a state machine execution, Step Functions uses the latest revision of the state machine definition.
State machine revisionA state machine can have one or more revisions. When you update a state machine using the UpdateStateMachine API action, it creates a new state machine revision. A revision is an immutable, read-only snapshot of a state machineâs definition and configuration. You can't start a state machine execution from a revision, and revisions don't have an ARN. Revisions have a revisionId, which is a universally unique identifier (UUID).
Testing with mocked service integrations
Versions
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4