What is the feature/update/fix?

Feature: Dual Load Balancer Support for Services

We've added the ability to expose services through both internal and external load balancers simultaneously. This new feature provides greater flexibility in service accessibility, allowing you to make a service available both within your VPC and to the public internet.

Previously, services could only be exposed through either an internal or external load balancer, but not both. This enhancement enables hybrid access patterns where certain services need to be accessible from both internal resources and external clients.

How to use it?

To enable dual load balancer access for a service, set the internalAndExternal attribute to true in your convox.yml:

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

Important Prerequisites:

• Your Rack must have the Internal parameter set to Yes:

  $ convox rack params set Internal=Yes
  

• This creates both an internal load balancer (accessible only within your VPC) and an external load balancer (accessible from the internet) for the specified service.

This is particularly useful for:

• Services that need to be accessed by both internal microservices and external clients
• API gateways that serve both public and private traffic
• Admin interfaces that require both VPC-internal access and controlled external access

Does it have a breaking change?

There are no breaking changes introduced with this feature. Existing services will continue to work as before. The internalAndExternal attribute is optional and defaults to false when not specified.

Requirements

To use this feature, you must:

• Be on at least rack version 20250822114342
• Have the Internal rack parameter set to Yes

You can check your rack's version with the command convox rack.
Update your rack to the latest version with the command convox rack update.