Access Amazon Verified Permissions using an interface endpoint (AWS PrivateLink) - Amazon Verified Permissions
ConsiderationsCreate an interface endpoint

Access Amazon Verified Permissions using an interface endpoint (AWS PrivateLink)

You can use AWS PrivateLink to create a private connection between your VPC and Amazon Verified Permissions. You can access Verified Permissions as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access Verified Permissions.

You establish this private connection by creating an interface endpoint, powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for Verified Permissions.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Considerations for Verified Permissions

Before you set up an interface endpoint for Verified Permissions, review Considerations in the AWS PrivateLink Guide.

Verified Permissions supports making calls to all of its API actions through the interface endpoint.

VPC endpoint policies are not supported for Verified Permissions. By default, full access to Verified Permissions is allowed through the interface endpoint. Alternatively, you can associate a security group with the endpoint network interfaces to control traffic to Verified Permissions through the interface endpoint.

Create an interface endpoint for Verified Permissions

You can create an interface endpoint for Verified Permissions using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Create an interface endpoint in the AWS PrivateLink Guide.

Create an interface endpoint for Verified Permissions using the following service name:

com.amazonaws.region.verifiedpermissions

If you enable private DNS for the interface endpoint, you can make API requests to Verified Permissions using its default Regional DNS name. For example, verifiedpermissions.us-east-1.amazonaws.com.