Playing with the Paths of Step functions

AWS Step Functions work by moving from one state to another state. States need a way to communicate with each other - DATA needs to be passed between them

Step Functions - AWS Service Integrations 2

In the previous post we successfully executed dynamo db, sqs and sns interactions directly from step functions. I wanted to try some tweaks to my state machine.

Step Functions - AWS Service Integrations

With all this serverless chatter around Lambda, the next thing was to try and orchestrate these Lambdas with Step Functions. Essentially a Step Function allows you to define the steps to be executed across systems in a visual UI. The interactions, retries, failure conditions and other orchestration behavior (or the flow management) can be done by Step Functions.

Using Lambda To Trigger a State Function

So I took the Hello World Step function example and wanted a Lambda to trigger the execution