So I need to scale out my web application, but I need to ensure the data between my droplets stays private. All the tutorials on Digital Ocean only describe setting iptables to limit who can access you droplets. My question is, shouldn’t encryption be used for communication between nodes as well as iptables? So that no third party droplet can eaves drop on the conversation between nodes? I don’t see that discussed at all as a best practice. If it isn’t needed, can someone fill me in as why this wouldn’t be needed. My biggest concern is SSL on MySql kills performance by between 15-25% and if someone can tell me it isn’t needed that would be great.

4 comments

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
3 answers

This question was answered by @CrypticDesigns:

I am not sure if its needed, don’t know the infrastructure. But an article has been posted earlier about this:
https://www.digitalocean.com/community/questions/private-networking-for-databse-server-or-public-network

View the original comment

I know this is old, but others might still find it (as I just did).

Soon, not any more, see:

https://www.digitalocean.com/community/tutorials/digitalocean-private-networking-faq

Hi there,

I just came across this question and decided to post a small update here in case that anyone else comes across this in 2020.

I would recommend considering the new DigitalOcean VPC networks.

VPC networks are completely isolated from both other customers and other VPCs on your own account. See here for more details:

https://www.digitalocean.com/docs/networking/vpc/

It’s also worth pointing out that DigitalOcean private networks provided account level isolation since July 18, 2018. The big changes with the release of VPCs are:

  • You can create multiple VPCs that are isolated from each other
  • You can define the IP range for your VPCs yourself

Source

Submit an Answer