Category: Lambda@Edge

In continuation with our series on Handling Redirects@Edge, in this blog post, we will explore how you can leverage Amazon CloudFront, Lambda@Edge and Amazon Simple Storage Service (S3) to offload the origin from URL redirection with more advanced capabilities. As part of this solution, we offer a simple custom-built user interface to define and manage […]

A HTTP URL redirect is a webserver function that redirects a user to a different URL from the one they originally requested. Redirections are useful when you want a short easy to remember URL which when accessed redirects you to the actual landing page. URL shortener services are a good example of this use case. […]

AWS for WordPress WordPress is a technological marvel in the number of internet sites it powers and the momentum with which developers actively contribute to the community. Recent estimates put WordPress at powering more than 34% of internet sites, and more than 50,000 plugins are available through WordPress.org covering everything from security enhancements to SEO […]

Amazon CloudFront allows you to create custom error pages for specific HTTP status codes and to change response codes. CloudFront also offers origin failover capability, with which you can easily set up failover logic between combinations of AWS origins or non-AWS custom HTTP origins. This creates minimal interruption in your viewer’s experience. However, while these […]

Enterprise customers who host private web apps on Amazon CloudFront may struggle with a challenge: how to prevent unauthenticated users from downloading the web app’s source code (for example, React, Angular, or Vue). In a separate blog post, you can learn one way to provide that security using Amazon Lambda@Edge and Amazon Cognito, with an example […]

Introduction Lambda@Edge is a feature of Amazon CloudFront that allows developers to implement custom logic for manipulating HTTP request/response exchanges or generating responses on the fly with low latency. Lambda@Edge empowers our customers with a full programming language (Node.js) to implement advanced logic. While customers often write stateless logic that is fully contained in Lambda@Edge […]

Introduction Werner Vogels, chief technology officer for AWS, has been quoted as saying: “Everything fails all the time.” Well, his quote applies as well to content delivery with Amazon CloudFront and Lambda@Edge. In content delivery, issues might occur in different places, for example: On your origin, when it returns HTTP 5xx errors On CloudFront, when […]

Just as with AWS Lambda, Lambda@Edge supports logging to CloudWatch, which can help you to troubleshoot your Lambda function code or to log custom data that is not available in CloudFront access logs.  Lambda@Edge functions are replicated around the world so CloudFront can invoke them closer to your end viewers, and CloudWatch log files for […]

As promised in my previous post of this series about Lambda@Edge, in this new blog post I’m sharing some best practices for managing a Lambda@Edge application. So how do you roll out code or configuration changes to a Lambda@Edge function and Amazon CloudFront distribution in a safe and controlled way? Over time, as your application evolves, you’ll […]

As of today, Application Load Balancers (ALBs) now support AWS Lambda functions as targets. Build websites and web applications as serverless code, using AWS Lambda to manage and run your functions, and then configure an ALB to provide a simple HTTP/S frontend for requests coming from web browsers and clients. Triggering a Lambda Function from […]