1

My issue was because my CloudFront origin was not in us-east, and when you auto-select your bucket's origin in CloudFront, it doesn't add the location prefix to the url. So make sure you add your s3 location like so: bucketname.s3.ap-east-1.amazonaws.com


1

I was struggling a bit with owned SSL Certificate and custom settings, but the following article really helped a lot: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/tutorial-redirecting-dns-queries.html Just had to read with attention to details... 502 bad gateway can be thrown only if the target is not reachable. Double check the origin and ...


1

The solution is uploading a separate robots.txt file for CloudFront URL. This will not block the CloudFront URL but will keep it away from google search Create robots_cf.txt file that contains this text: User-agent: * Disallow: / Now add this rule to .htaccess file (say Cloudfront URL is aaabbbcccddd.cloudfront.net): RewriteCond %{HTTP_HOST} ^...


Only top voted, non community-wiki answers of a minimum length are eligible