Customizing error handling in Step Functions

1

AWS Step Functions

If we have to coordinate multiple function calls, we can use AWS Step Functions to orchestrate the workflow. Step Functions integrates with many other AWS services, but here I'll focus on Lambda functions.

#Project Management #Workflow Automation #Web Service Automation 57 social mentions

2

Amazon SQS

When we use a queue which the function polls for messages, we usually apply some a retry mechanism. After an error has occurred, the function will attempt to get the task from the endpoint again with the same payload or parameters. If we are lucky, the call will be successful for the second or third time.

#Data Integration #Stream Processing #Web Service Automation 64 social mentions

3

Amazon SNS

The Next field contains the next state after Step Functions has caught any NotFoundError. In this case, it'll be the Send email notification state, which could be anything reasonable for the use case, for example, invoking another Lambda function or publishing a message to an SNS topic for the notification.

#Data Integration #Stream Processing #Web Service Automation 54 social mentions

4

AWS Lambda

Say we want to create a workflow that consists of multiple Lambda functions and maybe some other AWS services.

#Cloud Computing #Cloud Hosting #Backend As A Service 244 social mentions

5

AWS Identity and Access Management

When the first state (Get task from 3rd party) throws a NotFoundError, Step Functions will send an email notification with the error message to the subscribers before the execution fails. Don't forget to ALLOW the SNS:Publish action in the Step Function's IAM role if you choose to send a notification.

#Identity And Access Management #Identity Provider #SSO 52 social mentions