- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Did you check all the possible causes mentioned in this page? For example, you need to change your ALB's security group to allow inbound traffic from CloudFront.
504 error implies that Cloudfront is not getting timely reply from ALB. It may be due communication issue between Cloudfront and ALB. For this, check network ACL of ALB subnets (since you already checked ALB security group).
Second reason can be Cloudfront times out before getting reply from ALB. For this, check the latency of response given by ALB and if it is more than Cloudfront timeout-> increase cloudfront timeout or improve the ALB latency. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-504-gateway-timeout.html#http-504-gateway-timeout-configure-security-groups
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Yes I have checked the security group and allow the all traffic in security group but it's not working. It's throwing the error from cloud front.
Then did you use the right protocol? Depending on your distribution settings, your distribution might access the origin with HTTP or HTTPS protocol.