<p>Nginx will help you in performing the below items if you need some of them, Then I would say it make sense to add it to the stack </p>

<ul>
<li>Optimize the caching (you can also cache dynamic content.</li>
<li>Restrict access to the services (based on ips).</li>
<li>Implement basic auth for some services.</li>
<li>Load balancing traffic between different posds or services.</li>
<li>Rewrite URLS.</li>
<li>Pass extra headers or configs to the backend services.</li>
</ul>

CC BY-SA 4.0
2020-03-07T16:23:05.050Z
2020-03-07T16:23:05.050Z
Al-waleed Shihadeh
<p>Can anyone tell me if there's a "killer" reason to put NGINX in front Kubernetes pods running Gunicorn? </p>

<p>externally, I have CloudFront hitting an ELB which in turn engages the pods running Gunicorn with my Django based API server. </p>

<p>Since Caching is handled by CloudFront, and it's flexible enough for routing rules  -- is there any good reason to add NGINX to the mix? </p>

<nginx><amazon-cloudfront>
CloudFront -> ELB -> Pod running Gunicorn
JasonGenX
# CloudFront -> ELB -> Pod running Gunicorn

(Asked by: username_0 on 2020-02-21)

Can anyone tell me if there's a "killer" reason to put NGINX in front Kubernetes pods running Gunicorn?

externally, I have CloudFront hitting an ELB which in turn engages the pods running Gunicorn with my Django based API server.

Since Caching is handled by CloudFront, and it's flexible enough for routing rules -- is there any good reason to add NGINX to the mix?

**Tags:** nginx, amazon-cloudfront


---

## 1 answers

### Answer by username_1 on 2020-03-07. Score: 1 | Accepted answer

Nginx will help you in performing the below items if you need some of them, Then I would say it make sense to add it to the stack

* Optimize the caching (you can also cache dynamic content.
* Restrict access to the services (based on ips).
* Implement basic auth for some services.
* Load balancing traffic between different posds or services.
* Rewrite URLS.
* Pass extra headers or configs to the backend services.


---

