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).

Passing parameters to a service API in Step Functions

Use the Parameters field in a Task state to control what parameters are passed to a service API.

Inside the Parameters field, you must use the plural form of the array parameters in an API action. For example, if you use the Filter field of the DescribeSnapshots API action for integrating with Amazon EC2, you must define the field as Filters. If you don't use the plural form, Step Functions returns the following error:

The field Filter is not supported by Step Functions.

Pass static JSON as parameters

You can include a JSON object directly in your state machine definition to pass as a parameter to a resource.

For example, to set the RetryStrategy parameter for the SubmitJob API for Amazon Batch, you could include the following in your parameters.

"RetryStrategy": {
  "attempts": 5
}

You can also pass multiple parameters with static JSON. As a more complete example, the following are the Resource and Parameters fields of the specification of a task that publishes to an Amazon SNS topic named myTopic.

"Resource": "arn:aws-cn:states:::sns:publish",
  "Parameters": {
     "TopicArn": "arn:aws-cn:sns:us-west-2:account-id:myTopic",
     "Message": "test message",
     "MessageAttributes": {
       "my attribute no 1": {
         "DataType": "String",
         "StringValue": "value of my attribute no 1"
       },
       "my attribute no 2": {
         "DataType": "String",
         "StringValue": "value of my attribute no 2"
       }
     }
  },

Pass state input as parameters using Paths

You can pass portions of the state input as parameters by using paths. A path is a string, beginning with $, that's used to identify components within JSON text. Step Functions paths use JsonPath syntax.

To specify that a parameter use a path, end the parameter name with .$. For example, if your state input contains text within a node named message, you could pass that text as a parameter using a path.

Consider the following state input:

{
  "comment": "A message in the state input",
  "input": {
    "message": "foo",
    "otherInfo": "bar"
  },
  "data": "example"
}

To pass the value of the node named message as a parameter named myMessage, specify the following syntax:

"Parameters": {"myMessage.$": "$.input.message"},

Step Functions then passes the value foo as a parameter.

For more information about using parameters in Step Functions, see the following:

Pass Context object nodes as parameters

In addition to static content, and nodes from the state input, you can pass nodes from the Context object as parameters. The Context object is dynamic JSON data that exists during a state machine execution. It includes information about your state machine and the current execution. You can access the Context object using a path in the Parameters field of a state definition.

For more information about the Context object and how to access that data from a "Parameters" field, see the following: