AWS announces AWS Interconnect – multicloud (preview), providing simple, resilient, high-speed private connections to other cloud service providers. AWS Interconnect - multicloud is easy to configure and provides high-speed, resilient connectivity with dedicated bandwidth, enabling customers to interconnect AWS networking services such as AWS Transit Gateway, AWS Cloud WAN, and Amazon VPC to other cloud service providers with ease.
Connecting AWS VPC to another VPC by NAT-Instance
Connecting AWS VPC to another VPC by NAT-Instance:
my case is I want to use an application that connects to another cloud on AWS but it uses voice traffic like UDP and also normal data traffic, what is the resiliency of that architecture and the challenges that come with it along with scaling it up of course?
I have tried to use a public Linux EC2 to Route my private subnet to the internet to reach the other VPC using IPtables and IGW on AWS. I workers fine for now but for large scale what would it need?
- Language
- English
- Newest
- Most votes
- Most comments
Hi,
Why don't you just use a NAT gateway provided by AWS to do the address translation efficiently ? It will address for you all the hard stuff: scaling, resiliency, HA, etc.
See there to start : https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html
Best,
Didier
What are the types and approximate scale of numbers of parties connecting to each other? For example, are you the owner of a single service provider VPC, and there's an arbitrary number of customer VPCs connecting to your services, or you connecting to them to provide support ot other services from outside the customer VPCs? Is the total scale small enough to be handled by a single EC2 instance routing, NATing, or otherwise relaying it?
I can't Specify the Scale right now but it would be like Customer service to a third-party application, so not a small scale off course
What kind of problem did you have with the NAT gateway? If your need is only for simple outbound access, I do agree with Didier Durand's guidance that a NAT gateway should work for most types of traffic that don't require the traffic payload to be inspected or modified to reflect the adjustments from the address translation. It might fail with special types of traffic, like when the translated port mappings for idle UDP flows would have to be kept alive for longer than the 350 seconds that a NAT gateway persists them.
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
we tried but it won't work with specific Voice Protocols or Traffic