Authorizing requests with Lambda@Edge

1

Amazon Route 53

One drawback of Lambda function URLs is that they don't allow custom domains as of writing this. A workaround to this issue is to create a CloudFront distribution where the origin is the function URL. We can then add the distribution as a target for the Route 53 record.

#Domain Name Registrar #Cloud Computing #Domain Names 45 social mentions

2

AWS Lambda

Let's start with the Lambda@Edge function. Since it's just a regular Lambda function that AWS distributes and deploys to the edge locations, we can have a - more or less - standard Node.js code:.

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

3

Amazon CloudWatch

Originally the CloudWatch logs permissions look like this:.

#Monitoring Tools #Log Management #Application Performance Monitoring 54 social mentions

4

Amazon API Gateway

Lambda function URLs are a great choice for this purpose. They are easy to set up, and an API Gateway - although it's a proper solution - would probably be overkill here.

#API Tools #APIs #Web Service Automation 95 social mentions