serverlessrepo860114833029:applications/cloudfront-cdn">

A project that deploys a content delivery network (CDN) using AWS CloudFront for static assets hosted in a private S3 bucket.

This project creates the following resources:

• AWS::Certificate - *.<domain> SSL certificate
• AWS::Distribution - [http|https]://<domain> distribution
• AWS::Distribution - [http|https]://www.<domain> redirect distribution
• AWS::CloudFrontOriginAccessIdentity
• AWS::RecordSet - <domain> IPv4 DNS entry
• AWS::RecordSet - <domain> IPv6 DNS entry
• AWS::RecordSet - www.<domain> IPv4 DNS entry
• AWS::RecordSet - www.<domain> IPv6 DNS entry
• AWS::Bucket - private access log bucket
• AWS::Bucket - private static asset bucket
• AWS::Bucket - private bucket to redirect requests to https://<domain>
• AWS::BucketPolicy - only allow CloudFront to access static asset bucket
• AWS::Function - CloudFront Function for single page applications to redirect requests to /index.html
• AWS::Function - CloudFront Function to add various web security HTTP response headers

Installation

git clone https://github.com/smoketurner/sam-cdn.git
cd sam-cdn
npm install

Deploy

npm run build
npm run deploy

You can upload your static assets into the S3 bucket and Route53 and CloudFront will take care of any redirections and content serving for you.

References

• https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/example-function-add-index.html
• https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/example-function-add-security-headers.html
• https://www.awsadvent.com/2018/12/03/vanquishing-cors-with-cloudfront-and-lambdaedge/
• https://medium.com/faun/hardening-the-http-security-headers-with-aws-lambda-edge-and-cloudfront-2e2da1ae4d83