Report this

What is the reason for this report?

How to Use Load Balancer Internal IP To Avoid Unnecessary Bandwidth Charges

Posted on April 17, 2021

Hi, DigitalOcean load balancer seems to only have a public IP (no internal IP).

As far as I understand, if I were to send traffic from one droplet (consumer) to a service (few droplets BEHIND A LOAD BALANCER) on the SAME VPC, I would be charged for bandwidth although the consumer and the service are on the same VPC (because I would be using the load balancer public IP).

Is there a way to use the load balancer internal IP? Maybe a DNS name I’m unaware of?

Thank you



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

Hi,

DigitalOcean doesn’t provide internal load balancers. Their Load balancers are all publicly exposed, no way o use them internally

Hey!

Quick update here, you can now create internal-only regional load balancers.

Internal load balancers have no public IP address and are only accessible by resources in the same VPC.

This feature is currently in early availability and only available through the CLI and API.

- Bobby

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.