Score:0

Using Nginx reverse proxy with CloudFront

mn flag

We have a domain served by CloudFront and now we need to add a reverse proxy using Nginx (unfortunately the reverse proxying capabilities of CloudFront are insufficient for our use case). My question is, where should we put this Nginx server?

  1. Before CloudFront - In this case my fear is that we are completely loosing the benefits of the CDN. The entrypoint is Nginx which means we can't leverage the edge computing caching and improved latency of CloudFront, am I right?
  2. After CloudFront (as an origin) - In this case CloudFront is still the entrypoint and Nginx will be an origin server that performs reverse proxying. Using this configuration, are we still benefiting of CloudFront edge caching and improved latency?

Any other possible solution?

Score:0
ws flag

Yes, you lose much of the benefits of Clouflare (particularly the geo-aware caching) i you put a proxy in front ot Cloudflare. You would also need to solve some additional technical issues relating to DNS.

Using this configuration, are we still benefiting of CloudFront edge caching and improved latency?

Yes you still get a benefit from offloading cacheable content from your origin and geo-aware caching.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.