Step Function Callbacks with AWS Lambda | Console Tutorial

Step Function callbacks allow you to pause the execution of your workflow until an external actor performs a task. This is especially useful for workflows that require human involvement (e.g. a human validating an order) before allowing your workflow to resume. In this video, I show you how to use the Wait For Callback feature in combination with AWS Lambda. I show you how to set up your workflow, how to enable the feature, and how to resume your step function with input arguments that can be passed to the next state.

📚 My Courses 📚

🎉SUPPORT BE A BETTER DEV🎉

📚 MY RECOMMENDED READING LIST FOR SOFTWARE DEVELOPERS📚

🎙 MY RECORDING EQUIPMENT 🎙

💻 MY DESKTOP EQUIPMENT 💻

🌎 Find me here:

#SoftwareEngineer
#SoftwareDeveloper

[biswaranjansahoo]

Excellent demonstration with explanation of the failures with cause. You have done a lot of tries and came out with this one. Thank you so much, it clarifies WaitForTaskToken concept

[bharadhwajn]

4:47 Thanks for the video. The send task success API call can be made from inside the lambda as follows
(In Python for example)

sfn = boto3.client('stepfunctions')
sfn.send_task_success(taskToken=event['TaskToken'], output='output-message')

[squidwurrd]

Awesome video. Videos like this really unlock new capablities for me at least.

[reelingua]

I can't believe they don't have this pass/fail option in the UI automatically. It seems like a no-brainer. Thanks for the video.

[Ahmed-rlti]

Thanks for the video Daniel, interesting topic. I'm using this as a solution for my project but I rather prefer to see an automated methodology to return back the token without human involvement. Can you propose us a solution for that ?

[zijiali]

Hey Daniel,

Could stuff. Can you think of an actual application where it can make use of lambda callback feature?

[tahayusufkomur]

Hey Daniel, thanks for the video!

I am working as a data engineer and our team is in a process to decide what orchestrator to use. Airflow or AWS Step functions. Due to some limitations were not able to use MWAA and we don't want to meaintain the infrastructure. For that reason we decided to use AWS Step functions.

As a former Airflow user, I feel like Step Functions is much more complicated and many things are not out of package.

For example:
- naming your executions dynamically is not defaultly possible.
- fillback is not defaultly possible
- retriggering only a task via UI is not possible
- to create an intermediate step (ex python operator in airflow) is not possible here, you need to create an intermediate lambda function and include it externally

I am still discovering but currently little bit discouraged. What are your thoughts about these 2 tools?

[TheLostBijou]

So basically... if I understand you correctly, step functions can act as some sort of 'program'? THIS CHANGES EVERYTHING!!!!

[MikeNugget]

I hope I never have to use step functions

[farzadmf]

No offense to your video (which is great BTW), but this seems like a TERRIBLE design, hopefully it's an alpha or beta release or something!

$$.Task.Token is generating inside of sfn ? can not get the token on my handler