3 Answers
- Newest
- Most votes
- Most comments
2
Did you check all of the possible causes listed in the docs?
Do you have VPC Flow logs enabled, and does that give any indication as to what's happening?
0
Other than the above check list, you should also check if ALB has any whitelist of supported domain names, in this case your distribution supported domain name For example F5 LB can allow or deny certain HOST values if not explicitly whitelisted
answered 9 months ago
0
Besides documentation, you can refer to How do I troubleshoot a 502: "The request could not be satisfied" error from CloudFront?.
Are you accessing your ALB directly via HTTP or HTTPS? If this is HTTP only, edit your CloudFront Origin Protocol to HTTP only
You may also want to change CloudFront Behavior to CachingDisabled
Relevant content
- Accepted Answerasked 10 months ago
- asked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago