- A Cloud Guru
Moving an API Endpoint to AWS Lambda
Lambda is a great way to manage APIs in the cloud. In this lab, we will be transitioning an existing Node.js/Express API to AWS Lambda. This will allow you to get hands-on with the process of creating and configuring APIs in Lambda!
Table of Contents
Package the Application Code
Before starting the lab, ensure you download the
ctaws-plant-shopcode from the Github repository. There is already a Lambda-ready version of the code in that repository, in the directory
api/lambda. You can use CloudShell to work with the code, and doing so will make it easy to deploy the code to the Lambda function later.
You will need to download the dependencies, then package the code and dependencies in a
Create and Configure a Lambda Function
Create a Lambda function called
PlantShopAPI. This function should be accessible via a public URL with no need for authentication. It should also be connected to the default VPC, subnets, and the security group with the description
Plant Shop Security Group.
Deploy the packaged code to the function.
You will also need to supply the following environment variables to allow the function code to connect to the existing RDS database:
DB_HOST- Paste in the RDS database endpoint
What's a lab?
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.