Do the following to resolve this issue:
- Set up proper SSL certificate for your host.domain. You can do this with AWS Certificate Manager (ACM).
- Use the SSL certificate for the CNAME alias in the CloudFront distribution.
- Set the origin of the CloudFront distribution to point to the Elastic Beanstalk hostname.
- Create a CNAME record in Route 53 with the CloudFront distribution target (not an alias).
- Be sure that the certificate names and wildcards are accurate.
- Test the configuration without CloudFront first to make sure it works as expected.
Cloudfront Origin SecurityAccepted Answerasked 3 years ago
Lightsail container as CloudFront Origin returns 404 No Such ServiceAccepted Answerasked 7 months ago
elastic beanstalkasked 6 months ago
How is a CloudFront origin deemed unavailable?asked 6 months ago
How do I use Amazon CloudFront with AWS Elastic Beanstalk as the origin?Accepted AnswerEXPERTasked 3 years ago
Creating CloudFront Distribution, where do I enter my domain name?Accepted Answerasked a month ago
CloudFront with EIP as originAccepted Answerasked 2 years ago
Amazon CloudFront serving compressed files with Origin server running NGINXAccepted Answerasked 2 years ago
Can a CloudFront origin be another CloudFront distribution?asked 5 months ago
Can a CloudFront distribution have a chain of failover origins?asked 2 months ago