SonicWall AWS VPN – A Tutorial.
Recently I had to come up with a cloud-based project for a masters course I was taking at UMass Lowell (MSIT 5650 Cloud Computing). I decided to use a virtualized Windows Server 2016 on-premise host to connect Active Directory to Amazon AWS and Microsoft Azure in a variety of ways.
This tutorial covers creating a VPN between a SonicWall firewall and Amazon AWS to use an AWS EC2 Windows Server 2016 instance in an AWS VPC. This setup allowed me to create a domain trust between two AD domains (one on-premise and one in the AWS cloud) over a secure VPN connection.
- An AWS Account (Having free credit would be great, but costs are minimal if you don’t).
- A SonicWALL (I used a TZ300 with firmware 220.127.116.11-8n).
- An internet connection (A static IP would be best, but I used a dynamic assignment).
You’ll need an Amazon AWS account. If you already have an Amazon account, those credentials will work just fine. I won’t cover setting up an AWS account as those steps should be fairly easy to do. Head on over to aws.amazon.com to get started.
I used a TZ300 with 6.5 firmware – which has the newer/modern interface. Really any 5th or 6th generation SonicWall should suffice with firmware 5.8 / 5.9 or above.
A static IP would be best. I used a dynamic IP, and I didn’t experience any change in my IP address as I was working on this project over a few weeks. The IP I’m speaking of is the IP assigned (in my case by Comcast) to the SonicWall WAN (X1) interface. In the event your IP address does change, I will be pointing out where you would need to make any modifications in the setup.
The AWS Side:
- From the AWS Console, go to the VPC dashboard.