Explore >> Select a destination


You are here

fusionauth.io
| | initialcommit.com
2.9 parsecs away

Travel
| | In this article, we will be using Route 53 to publish a static site hosted using AWS S3 to a custom domain.
| | benjamincongdon.me
2.5 parsecs away

Travel
| | AWS is a great place to host static content: Bandwidth / hosting costs are very cheap if you're at "hobbyist" scale, you get great availability, and AWS gives you free SSL termination / certificate management for HTTPS if you get everything setup correctly.
| | wweb.dev
2.2 parsecs away

Travel
| | In this part we're going to add CloudFront to deliver our website content with low latency to the user. Afterward, we'll add a domain with HTTPs for our website...
| | willhaley.com
16.9 parsecs away

Travel
| My guide is largely based on the Deploying to Amazon S3 guide from Semaphore, but with some pre-requisite steps and fine-tuning to S3. Switching your DNS provider for your domain to Amazon's Route 53 may be a requirement. Depending on your DNS provider, your DNS configuration, and your willingness to jump through hoops like setting up a reverse proxy on another server, you may be forced to transfer your domain. You should absolutely read the DNS and hosting section of Amazon's Static Website Using a Custom Domain guide before proceeding.