Convox Racks are installed using best practices for privacy and security. In cases with exceptional needs for isolation, Convox offers a “private” Rack mode that is easy to configure.
Public vs. Private Racks
Convox Rack creates a cluster of server instances into which your apps are deployed. In the default “public” mode, these instances are connected to a public subnet. Security Groups are used to keep out unwanted inbound traffic, and outbound traffic to the Internet is unrestricted.
By contrast, server instances in a private Rack have no direct connection to the Internet. Inbound traffic is routed from the load balancer to a private subnet, and outbound traffic passes through a NAT gateway.
Installing a Private Rack
A Rack can be installed as private by setting the parameter
Yes in Console during Rack installation.
Converting an Existing Rack to Private
It’s not currently possible to toggle a rack between Public and Private due to how EFS mount targets work (one subnet per AZ at a time, so it’s not possible to switch from public to private subnets, or vice versa).
Why Use a Private Rack?
The benefits of running a Rack in private mode include:
Network Isolation: Private mode adds an extra layer of network security. The private subnet means all inbound traffic must pass through an ELB that explicitly listens only on known ports. The NAT gateway allows outbound traffic from the private subnet.
Static Outbound IP: The NAT gateway created to handle outbound traffic has a static IP address. This can be useful in cases where your applications need to make requests to services that require IP whitelisting.
Private networking mode requires the provisioning of up to three NAT gateways (one for each availability zone) which are charged based on time and traffic. This will increase the monthly cost of your rack. More pricing details can be found in the AWS docs.