How can I route all traffic to SonicWall AWS NSv using same VPC and different subnet ?

03/26/2020 9 People found this article helpful 477,925 Views

Description

AWS Virtual Private Cloud is the fundamental building block for your private network in AWS. Virtual Private Cloud (VPC) lets you provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define.

IP Addresses used in this article
IP Addresses used in this article
SonicWALL NSv
VPC SPACE	10.5.0.0/16
VPC NAME	NSv_AWS_VPC
WAN IP	X1 :10.5.0.0/24
LAN IP	X0:10.5.1.0/24
EC2 INSTANCE/MACHINE DIFF SUBNET	X0: 10.5.20.90

Resolution

Creating a EC2 Instance (10.5.20.90) which is using the same VPC behind X0 interface of SonicWall 10.5.1.0/24 and X1 interface of SonicWall 10.5.0.0/24 but different subnet(10.5.20.0/24). Navigate to EC2 Dashboard |INSTANCES.
Creating a route to the destination 0.0.0.0/0 and Target as SonicWall NSV LAN interface as the next hop and associate only LAN subnets in the Subnet Associations. Navigate to VPC Dashboard|Route Tables.
Adding an access rule to allow interesting traffic. Navigate to SonicWall NSv Firewall | Access Rule.
Adding a NAT rule to allow interesting traffic. Navigate to Firewall |NAT Rule.
Adding a route rule to forward interesting traffic.Navigate to Network|Routing.

NOTE: The local hosted Virtual Subnets will not be accessed through the Public ip .