Tag: Amazon CloudFront

Authorization, the function of specifying access rights to resources is often required to help protect restricted content in web applications. This post will show you how to implement a serverless authorization of viewers using Amazon CloudFront, Lambda@Edge and Amazon Cognito without modifying your origin resources.

In this blog post, we will provide an overview of the performance, security, and cost benefits you get when using CloudFront to serve dynamic and/or static assets from Amazon EC2. We will also walk through the exercise of configuring CloudFront for Amazon EC2 origins.

Adding security response headers is often achievable by modifications to your application configuration. In this blog we will focus on how to achieve the same result when you have an application that can’t be modified at the origin (e.g., a web site hosted in Amazon S3).

Today Lambda@Edge announces a new feature that allows you to do content-based routing. Now you can programmatically define the origin based on logic in your Lambda function. This enables you to route requests to different origins based on request attributes such as headers, query strings, and cookies. Read our blog post to learn about different use cases and how you can set this up within your own architecture.

This blog post was originally published November 6 2017 by Ronan Guilfoyle on the AWS Startups Blog. Read this step by step guide to get your WordPress site running better than ever and ready for any sudden traffic spikes.

This blog post was originally published November 1 2017 on Jeff Barr’s AWS Blog. Read more about CloudFront’s recent launch of its 100th Edge Location and its some of its notable highlights from the past year.

This blog post was originally published October 18 2017 by Ronnie Eichler on the AWS Compute Blog. Read more about how to use Lambda@Edge to be able to use CloudFront with an S3 origin access identity and serve a default root object on subdirectory URLs.