Azure Traffic Routing Template Infrastructure

An introductionary project to Azure that I created with the help of some reddit suggestions. The project includes the following components:

- Virtual Network (VNET)
- Virtual Machines (VMs)
- Network Security Group (NSG) Rules
- Subnets
- Public IP Address
- Virtual Network Interfaces (VNICS)

One of the VMs serves as a router between the other two, called RouterVM. Each of the remaining VMs is in its own separate subnet. The idea is that the two non-routing VMs can only communicate through the Routing VM. NSG Rules are established to restrict any other traffic communication.

The Routing VM has two network interface cards: one for talking to VM2 in SubnetA and the other for talking to VM3 in SubnetB.

I. Project Infrastructure

Project Schema

The Azure topology diagrams provide a visual representation of the configured VNET, Subnets, and associated components such as Public IP Addresses and VNICS for each VM.

II. SSH Connection

SSH tests via the terminal

The SSH tests demonstrate connectivity between different VMs using terminal commands.

How to SSH via a DNS Name

The provided script sets up DNS names for VM2 and VM3. VM2's DNS name (vm2-dns) resides in the www.understandnetworking.com private DNS Zone. This allows connection from RouterVM to VM2 using the private DNS Zone address and VM2's DNS Name.

III. Tips

1. Remember to change the name and password of your VMs; the credentials in the script are just for demonstration.
2. For RDP and SSH access to RouterVM without exposing it through a public IP, consider using Azure Bastion.