This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I created a S2S VPN tunnel between AWS and Azure and on the Azure side I have a Hub and Spoke. 5 Vnets are peered to the Hub Vnet. 4 are able to communicate with AWS but 1 is unable. How can I address this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 94%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
@Anonymous , Thanks for your question. Please make sure you have that VNET address space listed on the Local Network Gateway attached to your VPN Connection
The address space of the AWS VPC is listed on the LNG attached to the VPN connection. None of the address spaces of the 4 Vnets that are connecting properly is listed either
You should add the address spaces of your Azure VNETs on the AWS side as well.
Yes, did that already.
Did you make sure your peering connections are well configured to use the remote gateway on the spoke site and to use the VPN as transit Gateway on the Hub side?