Static Website Hosting - AWS CloudFront and S3 - Terraform

Learn how to host a website with your own custom domain, using AWS CloudFront and S3. This video contains two demos; firstly a step by step guide for how to deploy your website using the AWS Console, then we’ll do the same using infrastructure as code, more specifically Terraform.
Timestamps:
0:00 - Intro​
1:39 - What is CloudFront?
2:53 - Why should you use CloudFront?
4:36 - Demo (AWS Console)
20:06 - Demo (Terraform)
- Terraform Introduction video: • Terraform introduction
- Custom Domain (Route53) and Certificate (ACM) video: • AWS Route53 - Domain a...
- CloudFront Cache Policies docs: docs.aws.amazon.com/AmazonClo...
- AWS Edge locations docs: docs.aws.amazon.com/AmazonClo...
Code example: github.com/endre-synnes/youtu...
Subscribe button animation: touchtechnologyreview.com/sub...
Follow me on Github: github.com/endre-synnes

[@supriyochatterjee4095]

Great video, wish to see lots of videos on AWS Terraform in details with step by step explanations, please kindly make videos on AWS NETWORKING, S3,EC2, Backups, IAM Roles and everything related to AWS Infrastructure configuration and management using Terraform in details

[@EndreSynnes]

Thank you so much! 😄
Thank you for the suggestions, I will look into these AWS services using Terraform in future videos 😄

[@user-id5pu2gy4n]

Good tutorial, short, conceptual, and easy to understand, brother. I wonder about activating S3 static website hosting and blocking all public access. How can I set up my CloudFront to access objects in the bucket? The official documentation does not provide this scenario.

[@EndreSynnes]

Hi, I'm sorry for the late response.
Thank you so much! 😄
Just to clarify, you have enabled the "Static website hosting" feature on tour S3 bucket and also want to use CloudFront? If this is the case, I would say that enabling the "Static website hosting" feature on the S3 bucket partially defeats the purpose of setting up CloudFront in front of your S3 bucket. This is because the content will then be available on the S3 bucket URL anyways (bypassing CloudFront all together) without you being able to restrict who can assess it. I would suggest using a private bucket (as in my video), and setting up CloudFront. You could also set up WAF (docs.aws.amazon.com/waf/latest/developerguide/cloudfront-features.html) to further limit who can assess the content.
I hope this was helpful, and please let me know if I misunderstood your question 😄