Creating an interface VPC endpoint for Amazon Pinpoint
You can establish a private connection between your virtual private cloud (VPC) and an endpoint in Amazon Pinpoint by creating an interface VPC endpoint.
Interface endpoints are powered by AWS PrivateLink
For more information, see the AWS PrivateLink Guide.
Creating an interface VPC endpoints
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 Pinpoint supports the following service names:
-
com.amazonaws.
region
.pinpoint com.amazonaws.
region
.pinpoint-sms-voice-v2
If you turn on private DNS for an interface endpoint, you can make API requests to Amazon Pinpoint
using the default DNS name for the AWS Region, for example,
com.amazonaws.
. For more
information, see DNS hostnames in the AWS PrivateLink
Guide.us-east-1
.pinpoint
For a list of all the Regions and endpoints where Amazon Pinpoint is currently available, see AWS service endpoints in the Amazon Web Services General Reference.
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 Pinpoint actions for all principals on all resources.
{ "Statement": [ { "Principal": "*", "Action": [ "mobiletargeting:CreateCampaign", "mobiletargeting:CreateApp", "mobiletargeting:DeleteApp", ], "Effect": "Allow", "Resource": "*" } ] }