PrivateLink allows a virtual private cloud (VPC) to share resources with another VPC that is deployed in the same region. The two VPCs can belong to the same account or different accounts. This topic describes some common scenarios and procedure for using PrivateLink.
Service resources that are supported by PrivateLink
PrivateLink allows you to specify Classic Load Balancer (CLB), Application Load Balancer (ALB), and Network Load Balancer (NLB) instances as the service resources of endpoint services.
CLB instances: The CLB instances that serve as service resources must be pay-as-you-go internal-facing CLB instances.
ALB instances: The ALB instances that serve as service resources must be internal-facing ALB instances that use fixed IP addresses.
NLB instances: The NLB instances that serve as service resources must be internal-facing NLB instances.
Common scenarios
A VPC accesses services in another VPC that belongs to the same account. For more information, see the following topics:
A VPC accesses services in another VPC that belongs to another account. For more information, see Access services in a VPC that belongs to another account.
Procedure
Before you use PrivateLink, activate PrivateLink on the service details page.
The following figure shows the procedure for using PrivateLink.
