The Ultimate Guide to Static Websites with S3 and Terraform

1

Next.js

Next.js offers an option to generate a static HTML export for Next.js applications. Such an export can be uploaded as is to an S3 bucket configured as suggested here to serve a Next.js application through AWS. This is the approach I have used for the Next.js + Bootstrap and Next.js templates.

#Developer Tools #Web Frameworks #JavaScript Framework 919 social mentions

2

Amazon S3

AWS S3 has long been known as an effective way to host static websites and assets. Unfortunately, while it is easy to configure an S3 bucket to enable static file hosting, it is quite complicated to achieve the following:.

#Cloud Hosting #Object Storage #Cloud Storage 170 social mentions

3

Amazon Route 53

The last AWS service we need to configure to get our static website up and running is Route 53. Route 53 can be used to define the DNS records for our website. You can use Route 53 to register your domain name or configure a domain you have obtained from a different registrar.

#Domain Name Registrar #Domain Names #Cloud Computing 44 social mentions

4

Amazon CloudFront

In the previous step we have generated a TLS certificate for our website. However, there is no way to link this directly to the static website served by S3. Instead we need to use the CloudFront CDN, which will allow us to use a custom domain name, link this with our certificate and then serve the files we have stored on S3.

#CDN #Cloud Computing #Content Distribution 67 social mentions

5

AWS Certificate Manager

To achieve this, will require a few steps, but we can start with acquiring a TLS certificate. AWS provides these for free using the AWS Certificate Manager.

#Identity And Access Management #Network & Admin #Two Factor Authentication 23 social mentions