- Newest
- Most votes
- Most comments
I'd spent several days on this and could see from various forums that several others had hit the same problem. I have now resolved my particular issue so thought I would add the additional changes in case it helps anyone later.
My problem was that I didn't see in any of the articles that you now had to change your DNS hosting (I wasn't using Route 53) to ensure that there was now a CNAME pointing to the CloudFront distribution. I changed my DNS entry of quickbooksonlineexpert.co.uk from pointing at the S3 bucket, to now point to the CloudFront dist (987iouyoiy****.cloudfront.net)
As well as this I added index.html to the Default Root Object in the Dist.
Once the distribution had updated its Status, I could now access the site correctly on HTTPS
Relevant content
- asked 2 years ago
- asked 9 months ago
- asked 6 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago