![]() Once the resource is created, click Go to resource to navigate to your Virtual WAN resource. Specify a name for your Virtual WAN resource and click Review + CreateĬlick Create to start provisioning the Virtual WAN resource. Specify the resource group and region you wish to deploy the Virtual WAN resource to. Search for Virtual WAN and select it from the list in the marketplace. If you have already created these, you can skip to the next session.įirst, click the "Hamburger" icon and select Create a resource On the Azure side, first we need to create a Virtual WAN resource and a Virtual WAN Hub, which will contain our VPN Gateway. Note: It is recommended to start with the Virtual WAN side first since you cannot modify the IP address of a Customer Gateway in AWS Create Azure Virtual WAN and Virtual WAN Hub When everything is said and done, you'll end up with a diagram that conceptually looks something like this: ![]() The design itself is a bit interesting since AWS and Azure differ on how connections are established to remote peers. ![]() This is a quick reflection of the steps I took to establish two IPSec tunnels between AWS' VPG and Azure's Virtual WAN VPN Gateway, propagating routes dynamically via BPG and ensuring High Availability. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |