{"id":121,"date":"2024-02-15T13:38:57","date_gmt":"2024-02-15T12:38:57","guid":{"rendered":"https:\/\/virtutimilitari.click\/?p=121"},"modified":"2024-02-15T14:02:01","modified_gmt":"2024-02-15T13:02:01","slug":"the-correct-way-of-hosting-a-static-website-with-aws-s3-bucket-and-cloudfront-in-4-easy-steps","status":"publish","type":"post","link":"https:\/\/virtutimilitari.com\/index.php\/2024\/02\/15\/the-correct-way-of-hosting-a-static-website-with-aws-s3-bucket-and-cloudfront-in-4-easy-steps\/","title":{"rendered":"The correct way of hosting a static website with AWS S3 bucket and CloudFront in 4 easy steps"},"content":{"rendered":"

The Problem<\/h1>\n

There’s a lot of articles and tutorials on the Internet on how to host a static website with AWS S3, but most of them include two very common problems:<\/p>\n

Problem #1<\/strong>: Use AWS S3 static website hosting feature, but no Cloudfront. If you do that, you won’t have custom domain with SSL and therefore no https access to your website.<\/p>\n

\"\"<\/p>\n

Problem #2<\/strong>: Allow public access to the bucket (un-check “block all public access”). This is a bad practice because it may lead to security issues.<\/p>\n

\"\"<\/p>\n

The solution.<\/h1>\n

In this article we’ll explain the right way of doing it. We’re assuming you’re already familiar with AWS Management Console and DNS management. Let’s get to it:<\/span><\/p>\n

Step 1.<\/strong> Go to AWS Certificate Manager and issue a certificate for the domain you’d like to use for the website (e.g. mywebsite.com).<\/p>\n