AWS Compute Blog

Category: Amazon CloudFront

Securing Lambda Function URLs using Amazon Cognito, Amazon CloudFront and AWS WAF

This post is written by Madhu Singh (Solutions Architect), and Krupanidhi Jay (Solutions Architect). Lambda function URLs is a dedicated HTTPs endpoint for a AWS Lambda function. You can configure a function URL to have two methods of authentication: IAM and NONE. IAM authentication means that you are restricting access to the function URL (and […]

Proposed architecture

Lifting and shifting a web application to AWS Serverless: Part 2

In part 1, you learn if it is possible to migrate a non-serverless web application to a serverless environment without changing much code. You learn different tools that can help you in this process, like Lambda Web Adaptor and AWS Amplify. By the end, you have migrated an application into a serverless environment. However, if […]

API Gateway caching

Building well-architected serverless applications: Optimizing application performance – part 3

September 8, 2021: Amazon Elasticsearch Service has been renamed to Amazon OpenSearch Service. See details. This series of blog posts uses the AWS Well-Architected Tool with the Serverless Lens to help customers build and operate applications using best practices. In each post, I address the serverless-specific questions identified by the Serverless Lens along with the recommended best practices. See […]

Example asynchronous processing

Building well-architected serverless applications: Optimizing application performance – part 2

This series of blog posts uses the AWS Well-Architected Tool with the Serverless Lens to help customers build and operate applications using best practices. In each post, I address the serverless-specific questions identified by the Serverless Lens along with the recommended best practices. See the introduction post for a table of contents and explanation of the example application. PERF 1. Optimizing […]

Optimizing costs with the AWS Lambda Power Tuning tool

Optimizing the cost of serverless web applications

Web application backends are one of the most popular workload types for serverless applications. The pay-per-value model works well for this type of workload. As traffic grows, it’s important to consider the design choices and service configurations used to optimize your cost.

Serverless Laravel App with Lambda

The serverless LAMP stack part 4: Building a serverless Laravel application

Update: The complete blog series and supporting GitHub repository is now available: Part 1: Introducing the new Serverless LAMP stack Part 2: Scaling relational databases Part 3: Replacing the web server Part 4: Building a serverless Laravel application Part 5: The CDK construct library for the serverless LAMP stack Part 6: From MVC to serverless […]

Lambda authorizers

Building well-architected serverless applications: Controlling serverless API access – part 1

This series of blog posts uses the AWS Well-Architected Tool with the Serverless Lens to help customers build and operate applications using best practices. In each post, I address the nine serverless-specific questions identified by the Serverless Lens along with the recommended best practices. See the Introduction post for a table of contents and explanation of the example application. Security question […]

Bref fpm cycle

The Serverless LAMP stack part 3: Replacing the web server

Update: The complete blog series and supporting GitHub repository is now available: Part 1: Introducing the new Serverless LAMP stack Part 2: Scaling relational databases Part 3: Replacing the web server Part 4: Building a serverless Laravel application Part 5: The CDK construct library for the serverless LAMP stack Part 6: From MVC to serverless […]

Building a serverless URL shortener app without AWS Lambda – part 3

This is the final installment of a three-part series on building a serverless URL shortener without using AWS Lambda. This series highlights the power of Amazon API Gateway and its ability to directly integrate with services like Amazon DynamoDB. The result is a low latency, highly available application that is built with managed services and […]