Rack-to-Rack Communication

Rack-to-rack communication via internal router is available on AWS racks.

Using Convox’s internal_router rack parameter along with the service internalRouter attribute, you can enable private communication between racks/clusters on your cloud platform. You can complete this in a few steps:

Prerequisites

You can check your rack's version by running convox rack -r rackNAME.

You will first need to establish connectivity between your racks in your given cloud environment. Under standard conditions racks will be installed in separate VPCs. Connectivity is most commonly accomplished via VPC Peering and configuration of routes and security groups.

You will need to manually complete this setup process on your own as we cannot predict your existing infrastructure or how you would need to facilitate or secure this connection/peering to suit your requirements.

Enabling Rack-to-Rack Communication

Once connectivity is established you will need to set the internal_router rack parameter to true by running: convox rack params set internal_router=true -r rackNAME

• This will install the internal load balancer into the VPC that facilitates rack-to-rack communication.
• You can verify that the load balancer was created in your cloud environment by checking its applicable service page.

Finally, set your desired service to use this internal load balancer by configuring the service attribute internalRouter to true and deploy the application.

services:
  web:
    build: .
    port: 3000
    internalRouter: true
    environment:
      - PORT=3000

• You can verify that this service is being internally routed by running convox services -a appNAME and attempting to access the service URL from the public internet and again from a service within your VPC peered Rack.

See Also

• internal_router rack parameter for enabling the internal load balancer
• Service Discovery for intra-rack service communication