you can use something else, but on the subnet where I created the load balancer you should have something that forwards the traffic, you cannot refer directly to the target network
the easiest way is to correct the addressing in one of the networks, you can also do something similar to what I did Implement NAT either in the AWS VPC or on the on-premises network to translate the overlapping IP addresses into a non-conflicting range
Private NAT gateway can only be connected to one subnet. Let's say we have VPC1 and NAT-GW is connected here. We can connect to instances in VPC2 However when you want to connect from instances in VPC2 to VPC1, do you have to create a second NAT-GW in VPC2 ?
Yes, if the subnets have the same CIDR then you need to hide your subnet. You can create another NAT gateway for this purpose. It is also possible to use AWS PrivateLink or something else, but I focused here on NAT-GW.
Nat gateway is another point in the path that packets travel and can minimally extend it. If you are getting a timeout, it may be a configuration mistake. It's a good idea to use the Reachability Analyzer tool and see if there is a problem between the source and the destination.
This is a good post, but I'd recommend re-shooting the video. It is very fuzzy at the moment - one can't really make out what info you're adding into each screen.
wow thanks for this video, real life example and step by step instruction, it seems simpler now, thx 💖
No problem, thanks for feedback
Thanks for the real usage example, not just theory
No problem. New tutorial coming soon
Great movie. You have done a good job mate. :)
Thanks for feedback
dobra robota
Dzięki
What appliance are you using for the NAT? Can you post a tutorial on how that was configured?
I just use AWS NAT gateway. The configuration is simple, you can see it in this video from 6:32. Soon there will be an article about it on my blog.
thanks, so You need the Network Load Balancer too right? to route the destination through it
you can use something else, but on the subnet where I created the load balancer you should have something that forwards the traffic, you cannot refer directly to the target network
Hi Can you please share a solution for IP overlapping between AWS servers and onprem servers connectivity over IPsec VPN?
the easiest way is to correct the addressing in one of the networks, you can also do something similar to what I did Implement NAT either in the AWS VPC or on the on-premises network to translate the overlapping IP addresses into a non-conflicting range
Private NAT gateway can only be connected to one subnet.
Let's say we have VPC1 and NAT-GW is connected here.
We can connect to instances in VPC2
However when you want to connect from instances in VPC2 to VPC1, do you have to create a second NAT-GW in VPC2 ?
Yes, if the subnets have the same CIDR then you need to hide your subnet. You can create another NAT gateway for this purpose. It is also possible to use AWS PrivateLink or something else, but I focused here on NAT-GW.
Nat gateways are ruining my workflows , they are timing out my ec2 instances :(
Nat gateway is another point in the path that packets travel and can minimally extend it.
If you are getting a timeout, it may be a configuration mistake. It's a good idea to use the Reachability Analyzer tool and see if there is a problem between the source and the destination.
This is a good post, but I'd recommend re-shooting the video. It is very fuzzy at the moment - one can't really make out what info you're adding into each screen.
Thanks. I checked and in the highest resolution I did not notice such problems. At what point in the video did you notice the problem?