Learn R Programming

paws (version 0.1.12)

sfn: AWS Step Functions

Description

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 .

Usage

sfn(config = list())

Value

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.

Arguments

config

Optional configuration of credentials, endpoint, and/or region.

Service syntax

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

Operations

create_activityCreates an activity
create_state_machineCreates a state machine
delete_activityDeletes an activity
delete_state_machineDeletes a state machine
describe_activityDescribes an activity
describe_executionDescribes an execution
describe_state_machineDescribes a state machine
describe_state_machine_for_executionDescribes the state machine associated with a specific execution
get_activity_taskUsed by workers to retrieve a task (with the specified activity ARN) which has been scheduled for execution by a running state machine
get_execution_historyReturns the history of the specified execution as a list of events
list_activitiesLists the existing activities
list_executionsLists the executions of a state machine that meet the filtering criteria
list_state_machinesLists the existing state machines
list_tags_for_resourceList tags for a given resource
send_task_failureUsed by activity workers and task states using the callback pattern to report that the task identified by the taskToken failed
send_task_heartbeatUsed 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_successUsed by activity workers and task states using the callback pattern to report that the task identified by the taskToken completed successfully
start_executionStarts a state machine execution
start_sync_executionStarts a Synchronous Express state machine execution
stop_executionStops an execution
tag_resourceAdd a tag to a Step Functions resource
untag_resourceRemove a tag from a Step Functions resource
update_state_machineUpdates an existing state machine by modifying its definition, roleArn, or loggingConfiguration

Examples

Run this code
if (FALSE) {
svc <- sfn()
svc$create_activity(
  Foo = 123
)
}

Run the code above in your browser using DataLab