Explanation
Why the waste happens and who it affects.
For example:
- Using Standard Workflows for short-lived, high-frequency executions leads to excessive per-transition charges.
- Using Express Workflows for long-running processes (close to or exceeding the 5-minute limit) may cause timeouts or retries.
- Inefficient use of states - such as chaining many simple states instead of combining logic into a Lambda function-can increase cost in both workflow types.
- Overuse of payload-passing between states (especially in Express workflows) increases billed memory and therefore the GB-second duration charge.
Billing model
The pricing dimensions that drive this cost.
- Standard Workflows: Billed per state transition
- Express Workflows: Billed per request and by duration, with billed memory (in 64-MB increments) driven by the workflow definition size, Map or Parallel state use, and payload size
- Choosing the wrong workflow type or poorly structuring a workflow (e.g., excessive state transitions) can significantly inflate costs, especially under high execution volumes or when parallel states and payload sizes are not optimized.
How to detect
6 checks to find it in your estate.
- Express workflows frequently hit duration or payload limits
- Short-lived workflows are using Standard instead of Express
- The number of state transitions is unusually high relative to the business logic
- Simple sequential logic could be collapsed into a Lambda or intrinsic function
- Map and Parallel states are overused or not optimized
- Input/output payload sizes between states are larger than necessary
How to fix
6 ways to remove the waste.
- Choose Express workflows for short-lived, high-volume executions
- Use Standard workflows for long-running, infrequent executions
- Combine simple logic steps into a single Lambda or use intrinsic functions
- Use ResultPath, OutputPath, and Parameters fields efficiently to trim payloads
- Minimize use of unnecessary Map or Parallel states where linear processing suffices
- Benchmark costs and execution patterns using AWS Step Functions metrics
Documentation
Vendor references for pricing and configuration.