- Newest
- Most votes
- Most comments
Yes, it will work. You will need to set the cache behavior(s) sending traffic to the ALB origin to forward the "Host" header to the origin, instead of using the name of the origin ALB, which will necessarily have to be different from the name the user requested that is now pointing to CloudFront. This configuration will cause the TLS SNI CloudFront sends to the origin to contain the hostname that the user originally requested. This detail is documented here: https://docs.aws.amazon.com/whitepapers/latest/secure-content-delivery-amazon-cloudfront/origin-https-configuration.html
The way you can configure which headers in the original request are forwarded to the origin is explained in this documentation article: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/header-caching.html#header-caching-web
Hello dev
Follow the links to resolve the issue:
https://aws.amazon.com/cloudfront/custom-ssl-domains/
-
Ensure your ACM certificate for "www.domainB.com" is valid and not expired.
-
After updating your DNS record, allow some propagation time for the changes to take effect globally.
By following these steps, your users will be able to access your ALB content securely through "https://www.domainB.com" with the custom SSL certificate from ACM, while CloudFront handles content delivery and caching.
Relevant content
- Accepted Answerasked a year ago
- asked 4 months ago
- AWS OFFICIALUpdated 6 days ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you @Leo its working