Serverless architectures let cloud providers handle the burden of managing servers and scaling to meet demand. Costs can also be reduced because you only pay for the compute resources needed to handle requests instead of paying for idle servers waiting for requests to come in. In this Lab you will practice serverless web development with Python for AWS by testing and deploying a to-do list application that uses:

• AWS Serverless Application Model (SAM) to package and deploy the API code as Lambda functions behind an API Gateway
• Cognito user pools to handle user registration and sign in
• DynamoDB for persisting each users to-do list

Lab Objectives

Upon completion of this Lab you will be able to:

• Test, package, and deploy serverless Python applications following the AWS Serverless Application Model (SAM)
• Configure an Amazon Cognito user pool as an API Gateway authorizer
• Synchronize a local folder with Amazon S3 to publish a website

Lab Prerequisites

You should be familiar with:

• Working with Linux on the command-line
• Basic concepts of Amazon S3, Cognito, API Gateway, Lambda, DynamoDB, and AWS command-line interface (CLI)
• Experience developing in Python is beneficial but not required
• The Build AWS Serverless Web Applications With Python Course walks through a similar development scenario as this Lab and can be beneficial to watch

Lab Environment

Before completing the Lab instructions, the environment will look as follows:

After completing the Lab instructions, the environment should look similar to:

Updates

March 27th, 2020 - Inserted validation checks through the lab steps

February 18th, 2020 - Updated lab code repository to resolve an issue causing the source code files to not load onto the EC2 instance

January 3rd, 2020 - Updated lab startup procedure to resolve an issue causing the EC2 instance's Python virtual environment to not be created

January 10th, 2019 - Added a validation Lab Step to check the work you perform in the Lab

September 24th, 2018: Updated the Lab to workaround an issue with the moto AWS mock library now supporting newer versions of boto3