Private Network

May 9, 2019 831

Networking DNS

By:

myprogramingnotes

Setup:

Built a base image via packer.
This base image is used to set up my infrastructure (via ansilbe)
Terraform sets privatenetworking <https://www.terraform.io/docs/providers/do/r/droplet.html#privatenetworking> variable to true

Question:

why do are these droplets (configured via terraform) assigned a public ip?
why is their public ip reachable on the internet

Sign In to Comment

1 Answer

cr3ativeprogrammer May 10, 2019

Droplets always have public ip, they can have private ip if u choose to have private networking on.
you can always set firewall rules to deny public ip .

Report

myprogramingnotes May 10, 2019

Thanks for the response.

I know that DO does not implement VPC (at least not that I can see from the docs I have looked through). But coming from AWS, I find that the idea of a private network tied to private subnet is entrenched in my mental mode of understanding. And instances launched in private subnets do not have public ips.

I guess what threw me off is the word - private - and thus ended up mixing up private subnets and private networks.

since I am using ansible, I create a template that removes eth0 entry from /etc/network/interfaces from the droplets that need to be private.
Report
- cr3ativeprogrammer May 10, 2019
  
  you can always do sudo ifdown eth0
  and then sudo sytemctl restart networking.
  throwing eth0 form networking is not good idea :)
  
  Report

Have another answer? Share your knowledge.

Related