You can establish a private connection between your VPC and Amazon EBS by creating an
interface VPC endpoint, powered by AWS PrivateLink
We create an endpoint network interface in each subnet that you enable for the interface endpoint.
For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.
Considerations for Amazon EBS VPC
endpoints
Before you set up an interface VPC endpoint for Amazon EBS, review Considerations in the AWS PrivateLink Guide.
By default, full access to Amazon EBS is allowed through the endpoint. You can control access to the interface endpoint using VPC endpoint policies. You can attach an endpoint policy to your VPC endpoint that controls access to Amazon EBS. 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 Controlling access to services with VPC endpoints in the Amazon VPC User Guide.
The following is an example of an endpoint policy for Amazon EBS. When attached to an
endpoint, this policy grants access to all Amazon EBS actions on all resources, except snapshots
that are tagged with key Environment
and value Test
.
{
"Statement": [
{
"Effect": "Deny",
"Action": "ebs:*",
"Principal": "*",
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/Environment": "Test"
}
}
},
{
"Effect": "Allow",
"Action": "ebs:*",
"Principal": "*",
"Resource": "*"
}
]
}
Create an interface VPC endpoint for Amazon EBS
You can create a VPC endpoint for Amazon EBS using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Create a VPC endpoint in the AWS PrivateLink Guide.
Create a VPC endpoint for Amazon EBS using the following service name:
-
com.amazonaws.
region
.ebs
If you enable private DNS for the endpoint, you can make API requests to Amazon EBS using
its default DNS name for the Region, for example, ebs.us-east-1.amazonaws.com
.