Page MenuHomeDevCentral

Build a bastion - load balancers - private instances network topology
Open, NormalPublic

Description

Currently, a lot of servers have public IcannNet addresses.

This is not needed, as we can switch to a more secure network topology:

  • bastion: allow developers and operations to connect per SSH to other machines
  • load balancer: receive public IP to act as a reverse proxy or network balancer for traffic
  • back-end server: keep private IP

That would help to reduce the attack surface of services.

Event Timeline

dereckson triaged this task as Normal priority.Jun 3 2020, 17:36
dereckson created this task.
dereckson added a parent task: Unknown Object (Maniphest Task).

For Salt and Vault, we're already using the private network.

The last step is to switch the Docker engines to the private IP, so the Docker ports are bind there, and create one unified proxy (nginx or something else) for the different engines instead to have a nginx on each. That's well drafted in D2293.