AWS Step Functions

 

• AWS Step Functions is a web service that provides serverless orchestration for modern applications. It enables you to coordinate the components of distributed applications and microservices using visual workflows.

Concepts

• • Step Functions is based on the concepts of tasks and state machines.
    • A task performs work by using an activity or an AWS Lambda function, or by passing parameters to the API actions of other services.
    • A finite state machine can express an algorithm as a number of states, their relationships, and their input and output.
  • You define state machines using the JSON-based Amazon States Language.
  • A state is referred to by its name, which can be any string, but which must be unique within the scope of the entire state machine. An instance of a state exists until the end of its execution.
    • There are 8 types of states:
      • Task state – Do some work in your state machine. AWS Step Functions can invoke Lambda functions directly from a task state.
      • Choice state – Make a choice between branches of execution
      • Fail state – Stops execution and marks it as failure
      • Succeed state – Stops execution and marks it as a success
      • Pass state – Simply pass its input to its output or inject some fixed data
      • Wait state – Provide a delay for a certain amount of time or until a specified time/date
      • Parallel state – Begin parallel branches of execution
      • Map state – Adds a for-each loop condition
    • Common features between states
      • Each state must have a Type field indicating what type of state it is.
      • Each state can have an optional Comment field to hold a human-readable comment about, or description of, the state.
      • Each state (except a Succeed or Fail state) requires a Next field or, alternatively, can become a terminal state by specifying an End field.
  • Activities enable you to place a task in your state machine where the work is performed by an activity worker that can be hosted on Amazon EC2, Amazon ECS, or mobile devices.
  • Activity tasks let you assign a specific step in your workflow to code running in an activity worker. Service tasks let you connect a step in your workflow to a supported AWS service.
  • With Transitions, after executing a state, AWS Step Functions uses the value of the Next field to determine the next state to advance to. States can have multiple incoming transitions from other states.
  • State machine data is represented by JSON text. It takes the following forms:
    • The initial input into a state machine
    • Data passed between states
    • The output from a state machine
  • Individual states receive JSON as input and usually pass JSON as output to the next state.

• • A state machine execution occurs when a state machine runs and performs its tasks. Each Step Functions state machine can have multiple simultaneous executions.
  • State machine updates in AWS Step Functions are eventually consistent.
  • By default, when a state reports an error, AWS Step Functions causes the execution to fail entirely.
    • Task and Parallel states can have a field named Retry and Catch to retry an execution or to have a fallback state.
  • The Step Functions console displays a graphical view of your state machine’s structure, which provides a way to visually check a state machine’s logic and monitor executions.

Features

• • Using Step Functions, you define your workflows as state machines, which transform complex code into easy to understand statements and diagrams.
  • Step Functions provides ready-made steps for your workflow called states that implement basic service primitives for you, which means you can remove that logic from your application. States are able to:
    • pass data to other states and microservices,
    • handle exceptions,
    • add timeouts,
    • make decisions,
    • execute multiple paths in parallel,
    • and more.
  • Using Step Functions service tasks, you can configure your Step Functions workflow to call other AWS services.
  • Step Functions can coordinate any application that can make an HTTPS connection, regardless of where it is hosted—Amazon EC2 instances, mobile devices, or on-premises servers.
  • AWS Step Functions coordinates your existing Lambda functions and microservices, and lets you modify them into new compositions. The tasks in your workflow can run anywhere, including on instances, containers, functions, and mobile devices.
  • Nesting your Step Functions workflows allows you to build larger, more complex workflows out of smaller, simpler workflows.
  • Step Functions keeps the logic of your application strictly separated from the implementation of your application. You can add, move, swap, and reorder steps without having to make changes to your business logic.
  • Step Functions maintains the state of your application during execution, including tracking what step of execution it is in, and storing data that is moving between the steps of your workflow. You won’t have to manage state yourself with data stores or by building complex state management into all of your tasks.
  • Step Functions automatically handles errors and exceptions with built-in try/catch and retry, whether the task takes seconds or months to complete. You can automatically retry failed or timed-out tasks, respond differently to different types of errors, and recover gracefully by falling back to designated cleanup and recovery code.
  • Step Functions has built-in fault tolerance and maintains service capacity across multiple Availability Zones in each region, ensuring high availability for both the service itself and for the application workflow it operates.
  • Step Functions automatically scales the operations and underlying compute to run the steps of your application for you in response to changing workloads.
  • AWS Step Functions has a 99.9% SLA.
  • AWS Step Functions enables access to metadata about workflow executions so that you can easily identify related resources. For example, your workflow can retrieve its execution ID or a timestamp indicating when a task started. This makes it easier to correlate logs for faster debugging and to measure workflow performance data.
  • It also supports callback patterns. Callback patterns automate workflows for applications with human activities and custom integrations with third-party services.
  • AWS Step Functions supports workflow execution events, which make it faster and easier to build and monitor event-driven, serverless workflows. Execution event notifications can be automatically delivered when a workflow starts or completes through CloudWatch Events, reaching targets like AWS Lambda, Amazon SNS, Amazon Kinesis, or AWS Step Functions for automated response to the event.

How Step Functions Work

• • Orchestration centrally manages a workflow by breaking it into multiple steps, adding flow logic, and tracking the inputs and outputs between the steps.
  • As your applications execute, Step Functions maintains application state, tracking exactly which workflow step your application is in, and stores an event log of data that is passed between application components. That means that if networks fail or components hang, your application can pick up right where it left off.

• Amazon States Language
  • A JSON-based, structured language used to define your state machine, a collection of states, that can do work (Task states), determine which states to transition to next (Choice states), stop an execution with an error (Fail states), and so on.
  • When creating a state machine, only the States field is required in the JSON document.
• Security and Monitoring
  • AWS Step Functions can execute code and access AWS resources (such as invoking an AWS Lambda function). To maintain security, you must grant Step Functions access to those resources by using an IAM role.
  • Step Functions is a HIPAA eligible service and is also compliant with SOC, PCI, and FedRAMP.
  • Step Functions delivers real-time diagnostics and dashboards, integrates with Amazon CloudWatch and AWS CloudTrail, and logs every execution, including overall state, failed steps, inputs, and outputs.

Pricing

• • Step Functions counts a state transition each time a step of your workflow is executed. You are charged for the total number of state transitions across all your state machines, including retries.