Using CloudFront origin groups to increase availability on SPA deployments

Using CloudFront origin groups to increase availability on SPA deployments

Table of Contents Overview Services utilized Existing deployment Existing deployment availability Adding high-availability Amazon S3 bucket (cross region) OAI - Origin Access Identity Don’t let DNS be your dependency in HA design Lambda@Edge can be mighty slow to de-replicate Honorable mentions Handling index.html redirection Redirects Security Conclusion Overview Adding automated failover for your SPA deployment that is deployed to an associated AWS region is a simple, cost-effective way to increase site availability! In this post, we’ll cover the sometimes forgotten parts of Amazon CloudFront, Lambda@Edge (and purpose-driven functionality) along with Amazon S3 as native origin’s within an origin group.

Read More
Expand your security response headers using newly native Amazon CloudFront Response Headers!

Expand your security response headers using newly native Amazon CloudFront Response Headers!

It was recently (11/02/2021) announced that: Today, Amazon CloudFront is launching support for response headers policies. You can now add cross-origin resource sharing (CORS), security, and custom headers to HTTP responses returned by your CloudFront distributions. You no longer need to configure your origins or use custom Lambda@Edge or CloudFront functions to insert these headers.

Read More
Using Hugo & AWS CodePipeline, CodeBuild, CloudFront & S3 to deploy a static site

Using Hugo & AWS CodePipeline, CodeBuild, CloudFront & S3 to deploy a static site

Retrospective: blog deployment model Goal Deploy a personal blog (in this case, troydieter.com) using the below requirements. I’ve used other deployment models, such as CI/CD pipelines – namely Jenkins to deploy static sites. Previous to the below approach, Ghost blog was used in conjunction with Nginx.

Read More
Categories
Tags