VNS3 NATe - NAT Gateway

Welcome to this custom, pre-configured NAT-Gateway appliance built on the Cohesive Networks VNS3 Platform.

This is our NATe edition providing a NAT-Gateway at a lower price and comparable performance to the cloud platform NAT Gateways.

Our goal is to deliver a network tool that performs the basic NAT-Gateway functions but can be upgraded if needed, to the capabilities of a full VNS3 Application Security Controller. If you have any questions or comments please review the following links.

NO DATA TAXES!

There is no additional "taxation" for your data to pass through the NATe device - except for standard cloud traffic charges.

What is included?

This device includes firewall functions allowing outbound source and port NAT-ing and can limit outbound NAT to specific ports or destination addresses. Additionally, plugins can be used to provide outbound WAF or outbound URL filtering to a small "allow list" or via connection to a URL filtering service like Webroot's BrightCloud offering.

This configuration DOES NOT include multi-cloud, site-to-site connectivity, or a number of other capabilities provided by the VNS3 Application Security Controller. Traditionally VNS3 controllers are used to create ingress/egress service networks providing north/south and east/west connectivity and security for cloud based systems, as well as machine-to-machine VPN for full encryption of data-in-motion to, through, and across the clouds.

NOTE: All VNS3 controllers regardless of SKU (including this edition) can be live upgraded to provide any capabilities your cloud use-case requires. If more extensive networking and cloud edge capabilities are required (Contact Cohesive Networks)

How do I connect?

This appliance instance should be running in its own cloud subnet with a distinct routing table from other subnets. In the route table for the NATe instance - set a 0.0.0.0/0 route to the cloud network's Internet gateway. For other instances to use NATe as the NAT Gateway, their routing table should have a 0.0.0.0/0 route pointing to the NATe instance/network address.

What does this do for me?