AWS Step Functions - AWS GovCloud (US)

AWS Step Functions

AWS Step Functions makes it easy to coordinate the components of distributed applications as a series of steps in a visual workflow. You can quickly build and run state machines to execute the steps of your application in a reliable and scalable fashion.

How AWS Step Functions Differs for AWS GovCloud (US)

  • US Commercial regions supports FIPS and Non-FIPS endpoints.

  • US GovCloud East supports FIPS and Non-FIPS endpoints.

  • US GovCloud West only supports FIPS endpoints.

  • US Commercial regions only supports AWS PrivateLink for Non-FIPS endpoints.

  • US GovCloud East region supports AWS PrivateLink for FIPS and Non-FIPS endpoints.

  • US GovCloud West region only supports AWS PrivateLink for FIPS endpoints.

Documentation for AWS Step Functions

AWS Step Functions documentation.

ITAR Boundary

AWS GovCloud (US) has an ITAR boundary, which defines where customers are allowed to store ITAR-controlled data for this service in AWS GovCloud (US) Regions. To maintain ITAR compliance, you must place ITAR-controlled data on the applicable part of the ITAR boundary. If you do not have any ITAR-controlled data in AWS GovCloud (US) Regions, this section does not apply to you. The following information identifies the ITAR boundary for this service:

ITAR-Regulated Data Permitted ITAR-Regulated Data Not Permitted
  • Not applicable

  • No ITAR-regulated data can be entered, stored, or processed in AWS Step Functions.

  • AWS Step Functions metadata is not permitted to contain ITAR-regulated data. This metadata includes all of the configuration data that you enter when setting up and maintaining your workflows.

  • For example, do not enter ITAR-regulated data in the following fields:

    • State machine name

    • State machine definition

    • Activity name

    • Execution name