AWS PrivateLink for Amazon Location

With AWS PrivateLink for Amazon Location, you can provision interface Amazon VPC endpoints (interface endpoints) in your virtual private cloud (Amazon VPC). These endpoints are directly accessible from applications that are on premises over VPN and AWS Direct Connect, or in a different AWS Region over Amazon VPC peering. Using AWS PrivateLink and interface endpoints, you can simplify private network connectivity from your applications to Amazon Location.

Applications in your VPC don't need public IP addresses to communicate with Amazon Location interface VPC endpoints for Amazon Location operations. Interface endpoints are represented by one or more elastic network interfaces (ENIs) that are assigned private IP addresses from subnets in your Amazon VPC. Requests to Amazon Location over interface endpoints stay on the Amazon network. You can also access interface endpoints in your Amazon VPC from on-premises applications through AWS Direct Connect or AWS Virtual Private Network (AWS VPN). For more information about how to connect your Amazon VPC with your on-premises network, see the AWS Direct Connect User Guide and the AWS Site-to-Site VPN User Guide.

For general information about interface endpoints, see Interface Amazon VPC endpoints (AWS PrivateLink) in the AWS PrivateLink Guide.

Types of Amazon VPC endpoints for Amazon Location Service

You can use one type of Amazon VPC endpoint to access Amazon Location Service: interface endpoints (by using AWS PrivateLink). Interface endpoints use private IP addresses to route requests to Amazon Location from within your Amazon VPC, on premises, or from an Amazon VPC in another AWS Region by using Amazon VPC peering. For more information, see What is Amazon VPC peering? and Transit Gateway vs Amazon VPC peering.

Interface endpoints are compatible with gateway endpoints. If you have an existing gateway endpoint in the Amazon VPC, you can use both types of endpoints in the same Amazon VPC.

Interface endpoints for Amazon Location have the following properties:

Considerations when using AWS PrivateLink for Amazon Location Service

Amazon VPC considerations apply to AWS PrivateLink for Amazon Location Service. For more information, see Interface endpoint considerations and AWS PrivateLink quotas in the AWS PrivateLink Guide. In addition, the following restrictions apply.

AWS PrivateLink for Amazon Location Service doesn't support the following:

Amazon VPC endpoints:

You can submit up to 50,000 requests per second for each AWS PrivateLink endpoint that you enable.

Create an interface endpoint for Amazon Location Service

You can create an interface endpoint for Amazon Location Service 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.

There are six different VPC endpoints, one for each feature offered by Amazon Location Service.

For example:

com.amazonaws.us-east-2.geo.maps

After you create the endpoint, you have the option to enable a private DNS hostname. To enable, select Enable Private DNS Name in the Amazon VPC Console when you create the VPC endpoint.

If you enable private DNS for the interface endpoint, you can make API requests to Amazon Location Service service using its default Regional DNS name. The following examples show the default Regional DNS names format.

The previous DNS names are for IPv4 domains. The following IPV6 DNS names can also be used for interface endpoints.

Access Amazon Location API operations from Amazon Location interface endpoints

You can use the AWS CLI or AWS SDKs to access Amazon Location API operations through Amazon Location interface endpoints.

Example: Create a VPC endpoint

aws ec2 create-vpc-endpoint \
--region us-east-1 \
--service-name location-service-name \
--vpc-id client-vpc-id \
--subnet-ids client-subnet-id \
--vpc-endpoint-type Interface \
--security-group-ids client-sg-id

Example: Modify a VPC endpoint

aws ec2 modify-vpc-endpoint \
--region us-east-1 \
--vpc-endpoint-id client-vpc-endpoint-id \
--policy-document policy-document \ #example optional parameter
--add-security-group-ids security-group-ids \ #example optional parameter 
# any additional parameters needed, see PrivateLink documentation for more details

Update an on-premises DNS configuration

When using endpoint-specific DNS names to access the interface endpoints for Amazon Location, you don't have to update your on-premises DNS resolver. You can resolve the endpoint-specific DNS name with the private IP address of the interface endpoint from the public Amazon Location DNS domain.

Use interface endpoints to access Amazon Location without a gateway endpoint or an internet gateway in the Amazon VPC

Interface endpoints in your Amazon VPC can route both in-Amazon VPC applications and on-premises applications to Amazon Location over the Amazon network.

Create an Amazon VPC endpoint policy for Amazon Location

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

Example: Sample VPCe policy for accessing Amazon Location Service Places APIs:

{
	"Version": "2012-10-17",
	"Statement": [
		{
			"Sid": "Allow-access-to-location-service-places-opeartions",
			"Effect": "Allow",
			"Action": [
				"geo-places:*",
				"geo:*"
			],
			"Resource": [
				"arn:aws:geo-places:us-east-1::provider/default",
				"arn:aws:geo:us-east-1:*:place-index/*"
			]
		}
	]
}