Private Path service for VPC

Summary

Private Path service for VPC allows a provider’s service to connect on the IBM Cloud private network, providing secure communication between VPCs and supported IBM Cloud and third-party services. The provider first deploys their service on IBM Cloud and creates a Private Path network load balancer (NLB) to enable their service for private connectivity. Next, the provider creates a Private Path service to expose and control access to their service. After the Private Path service is verified and published, other accounts can then connect to the provider’s service through endpoint gateways.

For consumers to connect to a provider’s service, the provider must relay information to their consumers, such as the cloud resource name (CRN) that maps to the Private Path service and a port, if required. Consumers then privately connect to the service by creating a VPE gateway with the information provided. Next, the consumer's connection request is sent to the service provider for review (the default policy). If there is an account policy for the consumer, that policy takes precedence over the default policy (to review, permit, or deny access).

The consumer can now access the service privately from their VPC, and the provider can host and manage consumer’ connections from within their own VPCs.

Features