docs.aws.amazon.com Open in urlscan Pro
13.35.58.99  Public Scan

Form analysis
0 forms found in the DOM

Text Content

SELECT YOUR COOKIE PREFERENCES

We use essential cookies and similar tools that are necessary to provide our
site and services. We use performance cookies to collect anonymous statistics so
we can understand how customers use our site and make improvements. Essential
cookies cannot be deactivated, but you can click “Customize cookies” to decline
performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide
useful site features, remember your preferences, and display relevant content,
including relevant advertising. To continue without accepting these cookies,
click “Continue without accepting.” To make more detailed choices or learn more,
click “Customize cookies.”

Accept all cookiesContinue without acceptingCustomize cookies


CUSTOMIZE COOKIE PREFERENCES

We use cookies and similar tools (collectively, "cookies") for the following
purposes.


ESSENTIAL

Essential cookies are necessary to provide our site and services and cannot be
deactivated. They are usually set in response to your actions on the site, such
as setting your privacy preferences, signing in, or filling in forms.




PERFORMANCE

Performance cookies provide anonymous statistics about how customers navigate
our site so we can improve site experience and performance. Approved third
parties may perform analytics on our behalf, but they cannot use the data for
their own purposes.

Allow performance category
Allowed


FUNCTIONAL

Functional cookies help us provide useful site features, remember your
preferences, and display relevant content. Approved third parties may set these
cookies to provide certain site features. If you do not allow these cookies,
then some or all of these services may not function properly.

Allow functional category
Allowed


ADVERTISING

Advertising cookies may be set through our site by us or our advertising
partners and help us deliver relevant marketing content. If you do not allow
these cookies, you will experience less relevant advertising.

Allow advertising category
Allowed

Blocking some types of cookies may impact your experience of our sites. You may
review and change your choices at any time by clicking Cookie preferences in the
footer of this site. We and selected third-parties use cookies or similar
technologies as specified in the AWS Cookie Notice.

CancelSave preferences




UNABLE TO SAVE COOKIE PREFERENCES

We will only store essential cookies at this time, because we were unable to
save your cookie preferences.

If you want to change your cookie preferences, try again later using the link in
the AWS console footer, or contact support if the problem persists.

Dismiss


Contact Us
English


Create an AWS Account
 1. AWS
 2. ...
    
    
 3. Documentation
 4. Amazon VPC
 5. AWS PrivateLink

Feedback
Preferences


AMAZON VIRTUAL PRIVATE CLOUD


AWS PRIVATELINK

 * What is AWS PrivateLink?
    * Concepts

 * Get started
 * Access AWS services
    * Services that integrate
    * Create an interface endpoint
    * Configure an interface endpoint
    * Receive alerts for interface endpoint events
    * Delete an interface endpoint
    * Gateway endpoints
       * Endpoints for Amazon S3
       * Endpoints for DynamoDB

 * Access SaaS products
 * Access virtual appliances
    * Create a Gateway Load Balancer endpoint service
    * Create a Gateway Load Balancer endpoint

 * Share your services
    * Create an endpoint service
    * Configure an endpoint service
    * Manage DNS names
    * Receive alerts for endpoint service events
    * Delete an endpoint service

 * Identity and access management
    * How AWS PrivateLink works with IAM
    * Identity-based policy examples
    * Endpoint policies

 * CloudWatch metrics
 * Quotas
 * Document history

Gateway endpoints for Amazon DynamoDB - Amazon Virtual Private Cloud
AWSDocumentationAmazon VPCAWS PrivateLink
ConsiderationsCreate a gateway endpointControl access using IAM
policiesAssociate route tablesEdit the VPC endpoint policyDelete a gateway
endpoint


GATEWAY ENDPOINTS FOR AMAZON DYNAMODB

PDFRSS

You can access Amazon DynamoDB from your VPC using gateway VPC endpoints. After
you create the gateway endpoint, you can add it as a target in your route table
for traffic destined from your VPC to DynamoDB.

There is no additional charge for using gateway endpoints.

DynamoDB supports both gateway endpoints and interface endpoints. With a gateway
endpoint, you can access DynamoDB from your VPC, without requiring an internet
gateway or NAT device for your VPC, and with no additional cost. However,
gateway endpoints do not allow access from on-premises networks, from peered
VPCs in other AWS Regions, or through a transit gateway. For those scenarios,
you must use an interface endpoint, which is available for an additional cost.
For more information, see Types of VPC endpoints for DynamoDB in the Amazon
DynamoDB Developer Guide.

CONTENTS

 * Considerations
 * Create a gateway endpoint
 * Control access using IAM policies
 * Associate route tables
 * Edit the VPC endpoint policy
 * Delete a gateway endpoint


CONSIDERATIONS


 * A gateway endpoint is available only in the Region where you created it. Be
   sure to create your gateway endpoint in the same Region as your DynamoDB
   tables.

 * If you're using the Amazon DNS servers, you must enable both DNS hostnames
   and DNS resolution for your VPC. If you're using your own DNS server, ensure
   that requests to DynamoDB resolve correctly to the IP addresses maintained by
   AWS.

 * The rules for the security groups for your instances that access DynamoDB
   through a gateway endpoint must allow traffic to and from DynamoDB. You can
   reference the ID of the prefix list for DynamoDB in security group rules.

 * The network ACL for the subnet for your instances that access DynamoDB
   through a gateway endpoint must allow traffic to and from DynamoDB. You can't
   reference prefix lists in network ACL rules, but you can get the IP address
   range for DynamoDB from the prefix list for DynamoDB.

 * If you use AWS CloudTrail to log DynamoDB operations, the log files contain
   the private IP addresses of the EC2 instances in the service consumer VPC and
   the ID of the gateway endpoint for any requests performed through the
   endpoint.

 * Gateway endpoints support only IPv4 traffic.

 * The source IPv4 addresses from instances in your affected subnets change from
   public IPv4 addresses to private IPv4 addresses from your VPC. An endpoint
   switches network routes and disconnects open TCP connections. The previous
   connections that used public IPv4 addresses are not resumed. We recommend
   that you do not have any critical tasks running when you create or modify a
   gateway endpoint. Alternatively, test to ensure that your software can
   automatically reconnect to DynamoDB if a connection breaks.

 * Endpoint connections cannot be extended out of a VPC. Resources on the other
   side of a VPN connection, VPC peering connection, transit gateway, or AWS
   Direct Connect connection in your VPC cannot use a gateway endpoint to
   communicate with DynamoDB.

 * Your account has a default quota of 20 gateway endpoints per Region, which is
   adjustable. There is also a limit of 255 gateway endpoints per VPC.


CREATE A GATEWAY ENDPOINT


Use the following procedure to create a gateway endpoint that connects to
DynamoDB.

TO CREATE A GATEWAY ENDPOINT USING THE CONSOLE

 1.  Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

 2.  In the navigation pane, choose Endpoints.

 3.  Choose Create endpoint.

 4.  For Service category, choose AWS services.

 5.  For Services, add the filter Type: Gateway and select
     com.amazonaws.region.dynamodb.

 6.  For VPC, select the VPC in which to create the endpoint.

 7.  For Route tables, select the route tables to be used by the endpoint. We
     automatically add a route that points traffic destined for the service to
     the endpoint network interface.

 8.  For Policy, select Full access to allow all operations by all principals on
     all resources over the VPC endpoint. Otherwise, select Custom to attach a
     VPC endpoint policy that controls the permissions that principals have to
     perform actions on resources over the VPC endpoint.

 9.  (Optional) To add a tag, choose Add new tag and enter the tag key and the
     tag value.

 10. Choose Create endpoint.

TO CREATE A GATEWAY ENDPOINT USING THE COMMAND LINE

 * create-vpc-endpoint (AWS CLI)

 * New-EC2VpcEndpoint (Tools for Windows PowerShell)


CONTROL ACCESS USING IAM POLICIES


You can create IAM policies to control which IAM principals can access DynamoDB
tables using a specific VPC endpoint.

EXAMPLE: RESTRICT ACCESS TO A SPECIFIC ENDPOINT

You can create a policy that restricts access to a specific VPC endpoint by
using the aws:sourceVpce condition key. The following policy denies access to
DynamoDB tables in the account unless the specified VPC endpoint is used. This
example assumes that there is also a policy statement that allows the access
required for your use cases.

{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Sid": "Allow-access-from-specific-endpoint",
         "Effect": "Deny",
         "Action": "dynamodb:*",
         "Resource": "arn:aws:dynamodb:region:account-id:table/*",
         "Condition": { 
            "StringNotEquals" : { 
               "aws:sourceVpce": "vpce-11aa22bb" 
            } 
         }
      }
   ]
}

EXAMPLE: ALLOW ACCESS FROM A SPECIFIC IAM ROLE

You can create a policy that allows access using a specific IAM role. The
following policy grants access to the specified IAM role.

{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Sid": "Allow-access-from-specific-IAM-role",
         "Effect": "Allow",
         "Principal": "*",
         "Action": "*",
         "Resource": "*",
         "Condition": {
            "ArnEquals": {
               "aws:PrincipalArn": "arn:aws:iam::111122223333:role/role_name"
            }
         }
      }
   ]
}		

EXAMPLE: ALLOWS ACCESS FROM A SPECIFIC ACCOUNT

You can create a policy that allows access from a specific account only. The
following policy grants access to users in the specified account.

{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Sid": "Allow-access-from-account",
         "Effect": "Allow",
         "Principal": "*",
         "Action": "*",
         "Resource": "*",
         "Condition": {
            "StringEquals": {
               "aws:PrincipalAccount": "111122223333"
            }
         }
      }
   ]        
}


ASSOCIATE ROUTE TABLES


You can change the route tables that are associated with the gateway endpoint.
When you associate a route table, we automatically add a route that points
traffic destined for the service to the endpoint network interface. When you
disassociate a route table, we automatically remove the endpoint route from the
route table.

TO ASSOCIATE ROUTE TABLES USING THE CONSOLE

 1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

 2. In the navigation pane, choose Endpoints.

 3. Select the gateway endpoint.

 4. Choose Actions, Manage route tables.

 5. Select or deselect route tables as needed.

 6. Choose Modify route tables.

TO ASSOCIATE ROUTE TABLES USING THE COMMAND LINE

 * modify-vpc-endpoint (AWS CLI)

 * Edit-EC2VpcEndpoint (Tools for Windows PowerShell)


EDIT THE VPC ENDPOINT POLICY


You can edit the endpoint policy for a gateway endpoint, which controls access
to DynamoDB from the VPC through the endpoint. The default policy allows full
access. For more information, see Endpoint policies.

TO CHANGE THE ENDPOINT POLICY USING THE CONSOLE

 1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

 2. In the navigation pane, choose Endpoints.

 3. Select the gateway endpoint.

 4. Choose Actions, Manage policy.

 5. Choose Full Access to allow full access to the service, or choose Custom and
    attach a custom policy.

 6. Choose Save.

TO MODIFY A GATEWAY ENDPOINT USING THE COMMAND LINE

 * modify-vpc-endpoint (AWS CLI)

 * Edit-EC2VpcEndpoint (Tools for Windows PowerShell)

The following are example endpoint policies for accessing DynamoDB.

EXAMPLE: ALLOW READ-ONLY ACCESS

You can create a policy that restricts access to read-only access. The following
policy grants permission to list and describe DynamoDB tables.

{
  "Statement": [
    {
      "Sid": "ReadOnlyAccess",
      "Effect": "Allow",
      "Principal": "*",
      "Action": [
        "dynamodb:DescribeTable",
        "dynamodb:ListTables"
      ],
      "Resource": "*"
    }
  ]
}		

EXAMPLE: RESTRICT ACCESS TO A SPECIFIC TABLE

You can create a policy that restricts access to a specific DynamoDB table. The
following policy allows access to the specified DynamoDB table.

{
  "Statement": [
    {
      "Sid": "Allow-access-to-specific-table",
      "Effect": "Allow",
      "Principal": "*",
      "Action": [
        "dynamodb:Batch*",
        "dynamodb:Delete*",
        "dynamodb:DescribeTable",
        "dynamodb:GetItem",
        "dynamodb:PutItem",
        "dynamodb:Update*"
      ],
      "Resource": "arn:aws:dynamodb:region:123456789012:table/table_name"
    }
  ]
}


DELETE A GATEWAY ENDPOINT


When you are finished with a gateway endpoint, you can delete it. When you
delete a gateway endpoint, we remove the endpoint route from the subnet route
tables.

TO DELETE A GATEWAY ENDPOINT USING THE CONSOLE

 1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

 2. In the navigation pane, choose Endpoints.

 3. Select the gateway endpoint.

 4. Choose Actions, Delete VPC endpoints.

 5. When prompted for confirmation, enter delete.

 6. Choose Delete.

TO DELETE A GATEWAY ENDPOINT USING THE COMMAND LINE

 * delete-vpc-endpoints (AWS CLI)

 * Remove-EC2VpcEndpoint (Tools for Windows PowerShell)

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please
refer to your browser's Help pages for instructions.

Document Conventions
Endpoints for Amazon S3
Access SaaS products
Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of
it.



Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.





DID THIS PAGE HELP YOU?

Yes
No
Provide feedback

NEXT TOPIC:

Access SaaS products

PREVIOUS TOPIC:

Endpoints for Amazon S3

NEED HELP?

 * Try AWS re:Post 
 * Connect with an AWS IQ expert 

PrivacySite termsCookie preferences
© 2024, Amazon Web Services, Inc. or its affiliates. All rights reserved.


ON THIS PAGE

 * Considerations
 * Create a gateway endpoint
 * Control access using IAM policies
 * Associate route tables
 * Edit the VPC endpoint policy
 * Delete a gateway endpoint