AWS Step Functions is a service that lets you coordinate the components of distributed applications and microservices using visual workflows.
You can use Step Functions to build applications from individual components, each of which performs a discrete function, or task, allowing you to scale and change applications quickly. Step Functions provides a console that helps visualize the components of your application as a series of steps. Step Functions automatically triggers and tracks each step, and retries steps when there are errors, so your application executes predictably and in the right order every time. Step Functions logs the state of each step, so you can quickly diagnose and debug any issues.
Step Functions manages operations and underlying infrastructure to ensure your application is available at any scale. You can run tasks on AWS, your own servers, or any system that has access to AWS. You can access and use Step Functions using the console, the AWS SDKs, or an HTTP API. For more information about Step Functions, see the AWS Step Functions Developer Guide .
sfn(config = list())
A client for the service. You can call the service's operations using
syntax like svc$operation(...)
, where svc
is the name you've assigned
to the client. The available operations are listed in the
Operations section.
Optional configuration of credentials, endpoint, and/or region.
svc <- sfn(
config = list(
credentials = list(
creds = list(
access_key_id = "string",
secret_access_key = "string",
session_token = "string"
),
profile = "string"
),
endpoint = "string",
region = "string"
)
)
create_activity | Creates an activity |
create_state_machine | Creates a state machine |
delete_activity | Deletes an activity |
delete_state_machine | Deletes a state machine |
describe_activity | Describes an activity |
describe_execution | Describes an execution |
describe_state_machine | Describes a state machine |
describe_state_machine_for_execution | Describes the state machine associated with a specific execution |
get_activity_task | Used by workers to retrieve a task (with the specified activity ARN) which has been scheduled for execution by a running state machine |
get_execution_history | Returns the history of the specified execution as a list of events |
list_activities | Lists the existing activities |
list_executions | Lists the executions of a state machine that meet the filtering criteria |
list_state_machines | Lists the existing state machines |
list_tags_for_resource | List tags for a given resource |
send_task_failure | Used by activity workers and task states using the callback pattern to report that the task identified by the taskToken failed |
send_task_heartbeat | Used by activity workers and task states using the callback pattern to report to Step Functions that the task represented by the specified taskToken is still making progress |
send_task_success | Used by activity workers and task states using the callback pattern to report that the task identified by the taskToken completed successfully |
start_execution | Starts a state machine execution |
start_sync_execution | Starts a Synchronous Express state machine execution |
stop_execution | Stops an execution |
tag_resource | Add a tag to a Step Functions resource |
untag_resource | Remove a tag from a Step Functions resource |
update_state_machine | Updates an existing state machine by modifying its definition, roleArn, or loggingConfiguration |
if (FALSE) {
svc <- sfn()
svc$create_activity(
Foo = 123
)
}
Run the code above in your browser using DataLab