Creates a state machine. A state machine consists of a collection of
states that can do work (Task states), determine to which states to
transition next (Choice states), stop an execution with an error
(Fail states), and so on. State machines are specified using a
JSON-based, structured language.
sfn_create_state_machine(name, definition, roleArn, type,
loggingConfiguration, tags)[required] The name of the state machine.
A name must not contain:
white space
brackets < > \{ \} \\[ \\]
wildcard characters ? *
special characters \" # % \\ ^ | ~ \` $ & , ; : /
control characters (U+0000-001F, U+007F-009F)
[required] The Amazon States Language definition of the state machine. See Amazon States Language.
[required] The Amazon Resource Name (ARN) of the IAM role to use for this state machine.
Determines whether a Standard or Express state machine is created. If not set, Standard is created.
Defines what execution history events are logged and where they are logged.
Tags to be added when creating a state machine.
An array of key-value pairs. For more information, see Using Cost Allocation Tags in the AWS Billing and Cost Management User Guide, and Controlling Access Using IAM Tags.
Tags may only contain Unicode letters, digits, white space, or these
symbols: _ . : / = + - @.
svc$create_state_machine(
name = "string",
definition = "string",
roleArn = "string",
type = "STANDARD"|"EXPRESS",
loggingConfiguration = list(
level = "ALL"|"ERROR"|"FATAL"|"OFF",
includeExecutionData = TRUE|FALSE,
destinations = list(
list(
cloudWatchLogsLogGroup = list(
logGroupArn = "string"
)
)
)
),
tags = list(
list(
key = "string",
value = "string"
)
)
)
This operation is eventually consistent. The results are best effort and may not reflect very recent updates and changes.
CreateStateMachine is an idempotent API. Subsequent requests won't
create a duplicate resource if it was already created.
CreateStateMachine\'s idempotency check is based on the state machine
name and definition. If a following request has a different
roleArn or tags, Step Functions will ignore these differences and
treat it as an idempotent request of the previous. In this case,
roleArn and tags will not be updated, even if they are different.