Static Website Hosting - AWS CloudFront and S3 - Terraform

แชร์
ฝัง
  • เผยแพร่เมื่อ 28 พ.ย. 2024

ความคิดเห็น • 9

  • @vdemcak
    @vdemcak 2 หลายเดือนก่อน

    One of the best Terraform tutorials I've ever seen...

    • @EndreSynnes
      @EndreSynnes  2 หลายเดือนก่อน

      Thank you so much! 🤩

  •  4 หลายเดือนก่อน

    Perfect. Saved my life. I needed it and was doing it wrong.
    Thank you very much.👏👏👏

    • @EndreSynnes
      @EndreSynnes  4 หลายเดือนก่อน

      Thank you so much! Great to see it was helpful!😄

  • @supriyochatterjee4095
    @supriyochatterjee4095 8 หลายเดือนก่อน +1

    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
      @EndreSynnes  8 หลายเดือนก่อน +2

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

  • @TrầnQuốcBảo-o3f
    @TrầnQuốcBảo-o3f 24 วันที่ผ่านมา

    I configured successfully ec2 instance with running state and upload resource on aws server but I still cannot connect to its public IP

  • @JessadaSrimoon
    @JessadaSrimoon 6 หลายเดือนก่อน

    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
      @EndreSynnes  5 หลายเดือนก่อน

      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 😄