AWS VPN NAT alternative
0
Our standard deployment when we setup VPN with a customer require us to use NAT between our subnet and the customer’s subnet . We need to be independent regardless to the subnets that the customer use and we don’t want to extend our customer networks / subnets to our AWS Tenant Account ,therefore we will need to setup NAT between our internal network and the customer network . This appears to be not supported with AWS VPN and does not seem to be on roadmap. What are some alternatives or workaround that can be used?
asked 5 months ago22 views
1 Answers
1
Depending upon the level of connectivity required, a VPC endpoint(s) may work if you only need to expose a couple of host/services. https://docs.aws.amazon.com/vpc/latest/privatelink/endpoint-service.html
answered 5 months ago
Relevant questions
Transit Gateway - Multiple Subnet per AZ
asked 3 years agoAWS VPN NAT alternative
asked 5 months agoVPC subnet routing.
Accepted Answerasked 3 months agoSite-to-Site VPN - On-prem network connectivity across AWS VPC subnets?
asked 3 years agoVPN Connection Public IP
Accepted AnswerRestricting IPs for Lambda functions connected to VPCs
Accepted Answerasked a year agoStatic IP for lambda
Accepted Answerasked a year agoAWS Client VPN - my systems are in different subnets that are in different VPCs
asked 4 months agocloud-init not setting default route to NAT Gateway
asked 2 years agoEC2 instance in private subnet shows IPv4 address of NAT instance
asked 3 years ago