If the bucket has CloudFront in front of it and you want to require HTTPS access to the content (which S3 by itself doesn't support for website hosting), then it's not necessary to make the S3 bucket public.
You can make use of a CloudFront Origin Access Identity so that only CloudFront can access your bucket and direct access is blocked.
Thanks for your interest in our article and valuable comments.
We agree - it is not necessary to set S3 bucket permissions to public. It is really possible if you are using HTTPS and CloudFront Origin Access Identity.
Best,
Codica Team
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If the bucket has CloudFront in front of it and you want to require HTTPS access to the content (which S3 by itself doesn't support for website hosting), then it's not necessary to make the S3 bucket public.
You can make use of a CloudFront Origin Access Identity so that only CloudFront can access your bucket and direct access is blocked.
Hello Andrew,
Thanks for your interest in our article and valuable comments.
We agree - it is not necessary to set S3 bucket permissions to public. It is really possible if you are using HTTPS and CloudFront Origin Access Identity.
Best,
Codica Team