AWS compatibility¶
Stegflow exposes an AWS-compatible API: 32 actions with Signature v4 auth. Point the official AWS SDK or CLI at a Stegflow endpoint and it just works.
- Use the official AWS SDKs & CLI. Just change the endpoint URL.
- Your existing activity workers connect unchanged, with the same
GetActivityTask/SendTaskSuccess. - Run your existing ASL definitions with no rewrite.
To set up credentials and point a client at your instance, see Connect an AWS SDK or CLI.
API actions¶
Actions marked are callable with the official AWS SDKs and CLI; those marked are not implemented yet.
State machines¶
-
CreateStateMachine -
DescribeStateMachine -
UpdateStateMachine -
DeleteStateMachine -
ListStateMachines -
ValidateStateMachineDefinition
Versions and aliases¶
-
PublishStateMachineVersion -
DeleteStateMachineVersion -
ListStateMachineVersions -
CreateStateMachineAlias -
DescribeStateMachineAlias -
UpdateStateMachineAlias -
DeleteStateMachineAlias -
ListStateMachineAliases
Executions¶
-
StartExecution -
StartSyncExecution -
StopExecution -
DescribeExecution -
DescribeStateMachineForExecution -
ListExecutions -
GetExecutionHistory -
RedriveExecution -
TestState
Activities and task tokens¶
-
CreateActivity -
DescribeActivity -
DeleteActivity -
ListActivities -
GetActivityTask -
SendTaskSuccess -
SendTaskFailure -
SendTaskHeartbeat
Tags¶
Map runs (Distributed Map)¶
Known differences¶
Areas where Stegflow does not yet match AWS behavior:
- Variables inside intrinsic functions. AWS lets you reference
Assignvariables in an intrinsic function's arguments (for exampleStates.Format('Hello {}', $customer.name)); Stegflow does not resolve variables there yet. Inside an intrinsic,$…paths read the state input and$$…the context object. See Intrinsic functions. - Distributed Map. Only the inline
Mapstate is available. Distributed Map (ProcessorConfigwith"Mode": "DISTRIBUTED"and itsEXPRESSchild executions) is not implemented, so the map-run actions listed above return an explicit not-implemented error.