Amazon Connect and interface VPC endpoints (AWS PrivateLink) - Amazon Connect

Amazon Connect and interface VPC endpoints (AWS PrivateLink)

You can establish a private connection between your VPC and Amazon Connect by creating an interface VPC endpoint. Interface endpoints are powered by AWS PrivateLink, a technology that enables you to privately access Amazon Connect APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with the Amazon Connect APIs that integrate with AWS PrivateLink.

For more information, see the AWS PrivateLink Guide.

Creating an interface VPC endpoint for Amazon Connect

You can create an interface endpoint 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.

Amazon Connect supports the following service names:


  • com.amazonaws.region.profile

  • com.amazonaws.region.voiceid

  • com.amazonaws.region.wisdom

If you enable private DNS for an interface endpoint, you can make API requests to Amazon Connect using the default DNS name for the Region. For example, For more information, see DNS hostnames in the AWS PrivateLink Guide.

Creating a VPC endpoint policy

You can attach an endpoint policy to your VPC endpoint that controls access. The policy specifies the following information:

  • The principal that can perform actions.

  • The actions that can be performed.

  • The resources on which actions can be performed.

For more information, see Control access to services using endpoint policies in the AWS PrivateLink Guide.

Example: VPC endpoint policy

The following VPC endpoint policy grants access to the listed Amazon Connect Voice ID actions for all principals on all resources.

{ "Statement":[ { "Effect":"Allow", "Action":[ "voiceid:CreateDomain", "voiceid:EvaluateSession", "voiceid:ListSpeakers" ], "Resource":"*", "Principal":"*" } ] }