Shown below is the recommended deployment architecture where the dashboard has been deployed to one machine (whether locally or in the cloud), behind a reverse proxy. If you're looking for a load-balanced set up, see the Load Balancing section. Each module can live in their own machine, but we recommend that the machines communicate within an isolated network.
In detail, the relationship between the client/proxy/dashboard should be as the following graphic, in order to achieve an SSL-enabled deployment. The primary idea is that there is a Proxy Web Server which communicates using SSL to the Client while keeping sensitive data encrypted.
Add Comment