Refactoring of a static site deployment, from Terraform to AWS CDK

Refactoring of a static site deployment, from Terraform to AWS CDK

Refactoring of a static site deployment, from TF to AWS CDK Intro Personal projects are fun, especially when you have the flexibility to choose your provisioner. In my case, I initially deployed the static site via Terraform. I realized shortly after, that.. even though it did what I wanted it to.. it may not scale in the way that I’d like it to. This is where I shifted to rewrite it in AWS CDK (Cloud Development Kit) v2.x to allow for:

Read More
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
Categories
Tags