Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Handle Errors in Serverless Applications with AWS Step Functions

by | Jan 12, 2021

Wondering how to handle errors in serverless applications with AWS? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services for AWS users, and online service providers.

Today, let us see how to use AWS Step Functions to handle workflow runtime errors.

 

AWS Step Functions

It is a serverless orchestration service that easily coordinates multiple Lambda functions into flexible workflows that are easy to debug and easy to change.

Similarly, AWS Lambda is a compute service that runs code without provisioning or managing servers.

Lambda functions can fail in three cases:

  • An unhandled exception raise
  • Timeout
  • Out of memory

However, to avoid this, and to reduce the amount of error handling code we write, we can use AWS Step Functions. It creates a serverless workflow that supports function error handling.

To begin with, our Support Engineers suggest having an AWS account.

 

Handle Errors in Serverless Applications with AWS

In order to Handle Errors in Serverless Applications with AWS, our Support Techs follow a few steps. Lets us have a look at them in detail.

 

Step 1. Create a Lambda Function to Mock an API

In this step, we will create a Lambda function that will mock a few basic API interactions.

a. Open the AWS Management Console, Enter user name and password. Next, search and select Lambda to open the service console:
Handle Errors in Serverless Applications with AWS
b. Then choose, Create a function.

c. Leave Author from scratch selected. Next, configure the Lambda function as follows:

For Name, type MockAPIFunction.
For Runtime, choose Python 3.6.
For Role, select Create custom role.

A new IAM window will open. Leave the Role name as lambda_basic_execution and click Allow. We will automatically return back to the Lambda console.

Click the Create function option.

d. On the MockAPIFunction screen, scroll down to the Function code section. In the code window, replace all of the code with the following, then choose Save.

class TooManyRequestsException(Exception): pass
class ServerUnavailableException(Exception): pass
class UnknownException(Exception): pass

def lambda_handler(event, context):
statuscode = event[“statuscode”]
if statuscode == “429”:
raise TooManyRequestsException(‘429 Too Many Requests’)
elif statuscode == “503”:
raise ServerUnavailableException(‘503 Server Unavailable’)
elif statuscode == “200”:
return ‘200 OK’
else:
raise UnknownException(‘Unknown error’)

e. Once done, scroll to the top of the window and note its Amazon Resource Name (ARN) in the upper-right corner of the page.

Amazon Resource Names (ARNs) uniquely identify AWS resources and help track and use AWS items and policies across AWS services and API calls. We require an ARN to reference a specific resource from Step Functions.

 

Step 2. Create an AWS Identity and Access Management (IAM) Role

AWS Step Functions can execute code and access other AWS resources. To maintain security, we must grant Step Functions access to these resources using AWS Identity and Access Management (IAM).

  1. In another browser window, navigate to the AWS Management Console, search for IAM. Click IAM to open the service console.
  2. Click Roles, then choose Create Role:
    Handle Errors in Serverless Applications with AWS
  3. Then select type of trusted entity page, select Step Functions from the list, and then choose Next: Permissions:
    AWS Step Functions
  4. On the Attach permissions policy page, choose Next: Review.
  5. On the Review page, type step_functions_basic_execution for Role name and click Create role.
  6. The new IAM role is created and appears in the list beneath the IAM role for the Lambda function.

 

Step 3. Create a Step Functions State Machine

In this step, we will use the Step Functions console to create a state machine that uses a Task state with a Retry and Catch field to handle the various API response codes.

We will use a Task state to invoke the mock API Lambda function, which will return the API status code we provide as input into the state machine.

a. Open the AWS Step Functions console. On the Create a state machine page, select Author from scratch. In the Details section, name the state machine MyAPIStateMachine, and then select “I will use an existing role”.

b. Next, we will design a state machine that will take different actions depending on the response from the mock API. If the API cannot reach, the workflow will try again.

Replace the contents of the State machine definition section with the following code:

{
“Comment”: “An example of using retry and catch to handle API responses”,
“StartAt”: “Call API”,
“States”: {
“Call API”: {
“Type”: “Task”,
“Resource”: “arn:aws:lambda:REGION:ACCOUNT_ID:function:FUNCTION_NAME”,
“Next” : “OK”,
“Comment”: “Catch a 429 (Too many requests) API exception, and resubmit the failed request in a rate-limiting fashion.”,
“Retry” : [ {
“ErrorEquals”: [ “TooManyRequestsException” ],
“IntervalSeconds”: 1,
“MaxAttempts”: 2
} ],
“Catch”: [
{
“ErrorEquals”: [“TooManyRequestsException”],
“Next”: “Wait and Try Later”
}, {
“ErrorEquals”: [“ServerUnavailableException”],
“Next”: “Server Unavailable”
}, {
“ErrorEquals”: [“States.ALL”],
“Next”: “Catch All”
}
]
},
“Wait and Try Later”: {
“Type”: “Wait”,
“Seconds” : 1,
“Next” : “Change to 200”
},
“Server Unavailable”: {
“Type”: “Fail”,
“Error”:”ServerUnavailable”,
“Cause”: “The server is currently unable to handle the request.”
},
“Catch All”: {
“Type”: “Fail”,
“Cause”: “Unknown error!”,
“Error”: “An error of unknown type occurred”
},
“Change to 200”: {
“Type”: “Pass”,
“Result”: {“statuscode” :”200″} ,
“Next”: “Call API”
},
“OK”: {
“Type”: “Pass”,
“Result”: “The request has succeeded.”,
“End”: true
}
}
}

c. Find the “Resource” line in the “Call API” Task state (line 7). To update this ARN to the ARN of the mock API Lambda function, click on the ARN text and then select the ARN from the list.

d. Click refresh to have Step Functions create a state machine diagram that corresponds to the workflow. After reviewing the visual workflow, click Create state machine.

 

Step 4. Test Error Handling Workflow

To test the error handling workflow, we will invoke the state machine to call the mock API by providing the error code as input.

a. Initially, click Start execution.

b. A new execution dialog box appears, where we can enter input for the state machine. We will play the part of the API, and supply the error code that we want the mock API to return.

Replace the existing text with the code below, then choose Start execution:

{
“statuscode”: “200”
}

c. On the Execution details screen, click Input to see the input of the state machine. Next, click Output to view the result of the state machine execution.

On the other hand, we can see that the workflow interpreted statuscode 200 as a successful API call.

d. Under Visual workflow, we can see the execution path of each execution. Click on the “Call API” Task state and then expand the Input and Output fields in the Step details screen.

e. Then, click on the “OK” Task state in the visual workflow. Under Step details, we can see that the output of the previous step has been passed as the input to this step.

The OK state is a Pass state, which simply passed its input to its output, performing no work. Pass states are useful when constructing and debugging state machines.

 

Step 5. Inspect the Execution of the State Machine

a. Scroll to the top of the Execution details screen and click on MyAPIStateMachine.

b. Then we click on Start execution again, and provide the following input and then click Start execution.

{
“statuscode”: “503”
}

c. In the Execution event history section, we expand each execution step to confirm that the workflow behaved as expected.

We will notice that:

  1. Step Functions captured the Input
  2. That input was passed to the Call API Task state
  3. Call API Task state called the MockAPIFunction using that input
  4. The MockAPIFunction executed
  5. MockAPIFunction failed with a ServerUnavailableException
  6. The catch statement in the Call API Task state caught that exception
  7. The catch statement failed the workflow
  8. State machine completed its execution

d. Then, we will simulate a 429 exception. Scroll to the top of the Execution details screen and click on MyAPIStateMachine.

Provide the following input, and click Start execution:

{
“statuscode”: “429”
}

e. Now we will inspect the retry behavior of the workflow.

In the Execution event history section, expand each execution step once more to confirm that Step Functions tried calling the MockAPILambda function two more times, both of which failed. The workflow transition to the Wait and Try Later state.

Then, the Wait state uses brute force to change the response code to 200, and the workflow completes execution successfully.

f. Run one more instance of the workflow, and this time, provide a random API response that is not handled by the state machine:

{
“statuscode”: “999”
}

Inspect the execution again using the Execution event history. When complete, click on MyAPIStateMachine once more. In the Executions pane, we can see the history of all executions of the workflow.

 

Step 6. Terminate Resources

In this step, we will terminate the AWS Step Functions and AWS Lambda related resources.

Terminating resources that are not in active use reduces costs and is a best practice.

  1. At the top of the AWS Step Functions console window, click on State machines.
  2. Then, click on MyAPIStateMachine and select Delete. Confirm the action by selecting the Delete state machine in the dialog box.
  3. Next, we will delete the Lambda functions. Click Services in the AWS Management Console menu, then select Lambda.
  4. In the Functions screen, click on your MockAPIFunction, select Actions, and then Delete. Confirm the deletion by clicking Delete again.
  5. Lastly, we will delete the IAM roles. Click Services in the AWS Management Console menu, then select IAM.
  6. Select both of the IAM roles that we created, then click Delete role. Confirm the delete by clicking Yes, Delete on the dialog box.

We can now sign out of the AWS Management console.

[Stuck in between? We are available 24*7]

 

Conclusion

To conclude, combining AWS Step Functions with AWS Lambda makes it simple to orchestrate AWS Lambda functions for serverless applications. Today, we saw a method on how our Support Engineers handle errors in Serverless Applications with AWS Step Functions.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

AWS Support

Use your time to build great apps. Leave your servers to us.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.
AWS Support

Use your time to build great apps. Leave your servers to us.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.

Categories:

Tags:

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF