A company is migrating a legacy storefront web application to the AWS Cloud. The application is complex and will take several months to refactor. A solutions architect recommended an interim solution of using Amazon CloudFront with a custom origin pointing to the SSL endpoint URL for the legacy web application until the replacement is ready and deployed.
The interim solution has worked for several weeks. However, all browser connections recently began showing an HTTP 502 Bad Gateway error with the header
`X-Cache: Error from cloudfront.` Monitoring services show that the HTTPS port 443 on the legacy web application is open and responding to requests.
What is the likely cause of the error, and what is the solution?
walkwolf3
Highly Voted 3 years, 7 months agoJazz888
3 years, 4 months agosapien45
3 years, 3 months agolemist
Most Recent 2 years, 11 months agoborisgor
3 years, 5 months agomabalon
3 years, 6 months ago