Bind Private IPv4

A private IPv4 is bound to a load balancer when internal, private, or hybrid access is required. A load balancer with a private IPv4 acts as an internal load balancer, distributing internal traffic within the global VPC.

You should bind a private IPv4 to a load balancer when:

• The service is intended for internal access only The load balancer is used by resources within the same VPC and should not be exposed to the internet.

• Internal service-to-service communication Microservices or internal systems require a unified access point within the private network.

• Hybrid connectivity scenarios On-premises environments access cloud services through VPN or dedicated connections.

• Security requirements Keeping services private reduces the attack surface and improves network security.

Note

You can bind private IPs from subnets in the same region within the global VPC associated with the load balancer.

On the load balancer list page, go to Actions > Bind Private IPv4; or on the Details page, go to Information > Network configuration > Bind Private IPv4.

Select the desired subnet, select IPs and click Confirm. If no desired subnet is available, click New Subnet to create one.

Note

You can go to the Details page, Information > Network configuration > Private IP Address > Actions > Unbind to unbind the IP.