Used as boilerplate code to scaffold out a small serverless AWS application using Terraform which produces API Gateway routes, Lambda functions, and a DynamoDB table - includes correlating CloudWatch Logs.

1.) You'll need an AWS account and Terraform installed.
2.) Designed to be used with a domain name with a Hosted Zone in AWS Route 53. If you're using this repo without a domain name, rename the domain.tf file to domain.tf.txt so it's not included when running the terraform apply command.
3.) Run the cd api && npm i to install the NPM uuid package required for the API to run. While this repo could replace UUID with Math.random() or another randomizer, there is utility demonstrating how to deploy Lamdba functions with NPM packages.

Run terraform import aws_route53_zone.primary YOUR_ROUTE_53_ZONE_ID (Replace YOUR_ROUTE_53_ZONE_ID with your Route 53 Hosted Zone ID).

Rename the variable domain in variables.tf to whatever your domain name is, for example: yourdomainname.com. The variable domain in variables.tf creates an S3 bucket for uploading Lamdba function .zip files. S3 buckets are globally unique, so if you encounter an error creating the bucket you may need to edit the main.tf file and replace:

resource "aws_s3_bucket" "lambda_bucket" {
	bucket = var.domain
}

with

resource "aws_s3_bucket" "lambda_bucket" {
	bucket = "yourbucketname-xyz-123-random-words"
}

To support multiple deployments of this code (or a fork of this code) to AWS, I have littered the code with the label yourapp to support multiple functions, roles, and policies within the same AWS Account. Replace yourapp with your desired project name so you have the ability to deploy multiple versions (modified or not) of this repo within your AWS Account.

This repo demonstrates multiple ways of serving content from Lambda, some of which may be considered unconventional (serving HTML files from Lambda). This is for simplification purposes minimizing the need for mulitple sub-domains (www.yourdomainname.com and api.yourdomainname.com) to serve static assets from one subdowmain using a CloudFront distrubution backed by and S3 bucket, and the other from API Gateway and Lambda.