You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My apologies if this is something very basic, I'm new to nginx reverse proxy routing.
I would like to add an additional layer around nginx reverse proxy for improving security and to perform load-balancing and to add horizontal scaling. Say, for example, I have two servers running nginx-proxy serving the same docker containers/applications on port 80. I would like to route traffic between both the servers based on CPU load, memory utilization, traffic count, etc.
As of now, I mapped a domain name to server public IP address in the DNS records. Routing takes place within the server and nginx-proxy redirects the domain name to its appropriate application container.
For example:
example1.com -> server1 public IP -> port 80/443 -> nginx-proxy -> app container1
example2.com -> server1 public IP -> port 80/443 -> nginx-proxy -> app container2
... and so on.
Now, I want to add a load balancer for horizontal scaling. Say, for example, I have this nginx proxy server running in AWS. Instead of exposing the server's public IP, I would like to place an Elastic Load Balancer (ELB from AWS) in between open internet and the server and map ELB's IP to the domain name.
The below is the example of what I'm trying to achieve:
example1.com -> ELB public IP -> server1 IP -> port 80/443 -> nginx-proxy -> app container1
example2.com -> ELB Public IP -> server1 IP -> port 80/443 -> nginx-proxy -> app container2
... and so on.
Now, I'm trying to forward the host header/domain name information from ELB to the server. so the server will be able to recognize the domain name example1.com and route to the app container1 accordingly. So the ELB decides where to send the traffic to (server1 or server2) based on the load and nginx-proxy within the server recognizes the domainname to serve the container.
Is there a way to do this when using docker-gen?
The text was updated successfully, but these errors were encountered:
My apologies if this is something very basic, I'm new to nginx reverse proxy routing.
I would like to add an additional layer around nginx reverse proxy for improving security and to perform load-balancing and to add horizontal scaling. Say, for example, I have two servers running nginx-proxy serving the same docker containers/applications on port 80. I would like to route traffic between both the servers based on CPU load, memory utilization, traffic count, etc.
As of now, I mapped a domain name to server public IP address in the DNS records. Routing takes place within the server and nginx-proxy redirects the domain name to its appropriate application container.
For example:
example1.com -> server1 public IP -> port 80/443 -> nginx-proxy -> app container1
example2.com -> server1 public IP -> port 80/443 -> nginx-proxy -> app container2
... and so on.
Now, I want to add a load balancer for horizontal scaling. Say, for example, I have this nginx proxy server running in AWS. Instead of exposing the server's public IP, I would like to place an Elastic Load Balancer (ELB from AWS) in between open internet and the server and map ELB's IP to the domain name.
The below is the example of what I'm trying to achieve:
example1.com -> ELB public IP -> server1 IP -> port 80/443 -> nginx-proxy -> app container1
example2.com -> ELB Public IP -> server1 IP -> port 80/443 -> nginx-proxy -> app container2
... and so on.
Now, I'm trying to forward the host header/domain name information from ELB to the server. so the server will be able to recognize the domain name example1.com and route to the app container1 accordingly. So the ELB decides where to send the traffic to (server1 or server2) based on the load and nginx-proxy within the server recognizes the domainname to serve the container.
Is there a way to do this when using docker-gen?
The text was updated successfully, but these errors were encountered: