-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public endpoints or VPC peering? #13
Comments
+1 one this question. |
+1 one this question about vpc peered latency or public igw? |
Great question! These stats are based on RTT between IGW in source region and public DynamoDB endpoint in destination region. VPC peering is coming in the near future via one of the updates I am currently working on. |
That's nice to hear! Out of interest, how would you do that? With DynamoDB having public endpoints they'd usually go across public internet as far as I know, can you use VPC endpoints and access these cross region? |
Cross-region VPC peering + VPC endpoints should enable this. I'm really curious to see the difference between public/private routing 👍 |
Hitting gateway style VPC Endpoints (Dynamo DB or S3) will not work across VPC peering. Your best bet would be using any of the interface style VPC Endpoints from this list: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html |
I was wondering what networking this was using as well. It could be super helpful to clarify that the current page is using internet latencies in both the website and the read me! Also I hope that you plan is to retain the internet latency and add the VPC peering (AWS Backbone) numbers rather than replace the internet latency. Having both helps with smaller budget implementations that can't step up to an AWS backbone implementation due to cost or complexity. |
Have a look at the AWS VPC FAQ:
Therefore from a network path perspective traffic from a Lambda function in region A to the public endpoint of DynamoDB in region B will take the same AWS backbone path as if you would create VPC peering or TGW peering between the regions and use a different private endpoint instead of DynamoDB. In neither of these two cases would traffic traverse the public Internet. |
Are the latency tests performed using DynamoDB public endpoints? So the packets are going across public internet? Or do you have VPC peering set up between regions?
The text was updated successfully, but these errors were encountered: