Setting Up Step Functions Local (Downloadable Version) - Java Version - Amazon Step Functions
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Setting Up Step Functions Local (Downloadable Version) - Java Version

The downloadable version of Amazon Step Functions is provided as an executable JAR file and as a Docker image. The Java application runs on Windows, Linux, macOS, and other platforms that support Java. In addition to Java, you need to install the Amazon Command Line Interface (Amazon CLI). For information about installing and configuring the Amazon CLI, see the Amazon Command Line Interface User Guide.

To set up and run Step Functions on your computer
  1. Download Step Functions using the following links.

    Download Links Checksum
    .tar.gz .tar.gz.md5
    .zip .zip.md5
  2. Extract the .zip file.

  3. Test the download and view version information.

    $ java -jar StepFunctionsLocal.jar -v Step Function Local Version: 2.0.0 Build: 2024-05-18
  4. (Optional) View a listing of available commands.

    $ java -jar StepFunctionsLocal.jar -h
  5. To start Step Functions on your computer, open a command prompt, navigate to the directory where you extracted StepFunctionsLocal.jar, and enter the following command.

    java -jar StepFunctionsLocal.jar
  6. To access Step Functions running locally, use the --endpoint-url parameter. For example, using the Amazon CLI, you would specify Step Functions commands as follows:

    aws stepfunctions --endpoint-url http://localhost:8083 command
Note

By default, Step Functions Local uses a local test account and credentials, and the Amazon Region is set to US East (N. Virginia). To use Step Functions Local with Amazon Lambda, or other supported services, you must configure your credentials and Region.

If you use Express workflows with Step Functions Local, the execution history will be stored in a log file. It is not logged to CloudWatch Logs. The log file path will be based on the CloudWatch Logs log group ARN provided when you create the local state machine. The log file will be stored in /aws/states/log-group-name/${execution_arn}.log relative to the location where you are running Step Functions Local. For example, if the execution ARN is:

arn:aws:states:us-east-1:123456789012:express:test:example-ExpressLogGroup-wJalrXUtnFEMI

the log file will be:

aws/states/log-group-name/arn:aws:states:us-east-1:123456789012:express:test:example-ExpressLogGroup-wJalrXUtnFEMI.log