CloudFront in Front of ELB and Kubernetes – Fixing Default Backend Issue with Nginx Ingress

amazon-cloudfrontamazon-elbamazon-web-servicesingresskubernetes

Having kubernetes cluster with nginx ingress, pointed to AWS ELB load balancer and Route 53 domain pointed to this ELB is working just fine. Now I am trying to add cloudfront, it's pointing to load balancer, but it shows 404 Default backend all the time. It seems cloudfront is not passing domain correctly, or am I missing something else?

Best Answer

A quick search surfaced an Amazon support article that claims you must whitelist headers in order for CloudFront to pass them along, and apparently host: is not one that is in the default whitelist

There's a similar question which discusses some more scenarios

Related Solutions

CloudFront with Custom Origin and ELB

It's possible that CloudFront doesn't handle multiple headers with the same name correctly and isn't seeing your max-age directive. According to this CloudFront does use the Expires header if present, so try getting your origin server to set that instead (preferably relative to the request time). For Apache I think you want something like this with mod_expires:

ExpiresDefault "access plus 1 hour"

Nginx Proxy to AWS ELB not passing HTTPS protocol to Backend Instances

ok, I figured it out! I just added an additional directive to the SSL block:

proxy_set_header X-Forwarded-Ssl on;

After restarting nginx, all requests are now passed as https to my ELB and app servers behind it!

Also, for my ELB listeners, I deleted the SSL (Secure TCP) listerner and added:

LB Protocol: HTTPS (Secure HTTP), LB Port: 443, Instance Protocol: HTTP, Instance Port: 80

Best Answer

Related Solutions

CloudFront with Custom Origin and ELB

Nginx Proxy to AWS ELB not passing HTTPS protocol to Backend Instances

Related Topic