All Services

Serverless

AWS Step Functions

AWS Step Functions coordinates distributed applications and business processes as observable state machines with service integrations, retries, waits, branching, parallelism, and human callback patterns.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with AWS Step Functions.

AWS Step Functions pricing and cost programs

Pricing model: Workflow execution usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: State transitions · Express request count · Express duration and memory

Programs and modes: Standard Workflows · Express Workflows

Standard and Express workflows use different billing dimensions.

Free Tier: Available — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement AWS Step Functions?

  • Makes workflow state, branching, retries, error paths, parallel work, and execution history explicit instead of hiding orchestration in application code and database flags.
  • Integrates directly with AWS services and SDK APIs, reducing Lambda glue code for service calls, long-running jobs, callbacks, and distributed-map processing.
  • Offers durable Standard workflows for long-running auditable processes and high-volume Express workflows for short idempotent event processing.

How to implement AWS Step Functions

  1. Choose Standard for durable, auditable, up-to-one-year workflows and non-idempotent coordination; choose Express for up-to-five-minute high-volume work whose execution semantics and integration limits are acceptable.
  2. Define the Amazon States Language state machine with small inputs and outputs, explicit ResultPath or output transformations, service integrations, retry and catch policies, timeouts, heartbeats, and terminal failures.
  3. Create a least-privilege execution role, deploy with infrastructure as code, enable appropriate logging and tracing, alarm on failures and throttling, and test replay, redrive, duplicate, timeout, and partial-failure cases.

AWS Step Functions best practices

  • Keep tasks idempotent when they can be retried, distinguish business failures from transient faults, use exponential backoff with jitter where supported, and set both workflow and task timeouts.
  • Store large payloads in S3 and pass references, control execution-history growth, split very large workflows, and use Distributed Map only when its concurrency and downstream capacity are understood.
  • Use optimized service integrations instead of unnecessary Lambda wrappers, restrict the execution role, avoid sensitive data in execution history or logs, and monitor failed, timed-out, throttled, and long-running executions.

AWS Step Functions use cases and server impact

  • Order, payment, and fulfillment workflows
  • Data and machine-learning pipelines
  • Human approvals and long-running job coordination

Replaces custom orchestration workers, cron chains, and workflow-state tables, while each task's correctness, idempotency, permissions, and downstream capacity remain application responsibilities.

Official implementation resources

Commonly paired AWS services

Architecture patterns using this service

Planning guides that use AWS Step Functions