Agents Choose When; Step Functions Keeps the Workflow’s Steps
AWS has made existing Standard and Express Step Functions workflows callable as tools through Amazon Bedrock AgentCore Gateway, an agent gateway . The key design boundary is simple but consequential: an agent chooses whether to invoke a workflow and what input to pass; the configured state machine determines which steps run and in what order. The connector’s two jobs In its October 29 announcement , AWS describes using existing Standard and Express workflows as agent tools. The gateway exposes workflow operations to an agent; Step Functions runs the state machine as configured. This creates an action boundary, not a way for a model to rewrite the business process while it runs. The connector documentation lists ten operations. Four are pinned to a state machine: StartExecution, StartSyncExecution, ListExecutions and DescribeStateMachine.
Read the full story on ForkastBeCrypto News shows a short excerpt and links to the publisher. The full report belongs to Forkast.






