/explore
|
You are here 
|
initialcommit.com | ||
| | | | |
benjamincongdon.me
|
|
| | | | | 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
|
|
| | | | | In this series, we're creating a serverless stack using AWS. In this part, I'll show how to serve a static website through an S3 Bucket and how to deploy from your local machine... | |
| | | | |
willhaley.com
|
|
| | | | | 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. | |
| | | | |
blog.atj.me
|
|
| | | The personal blog of Adam Jarret | ||
