Traffic Distributor is available as a Marketplace package and can be installed in a few steps. During installation, you can choose the entry point, number of NGINX balancers, routing method, traffic ratio, HTTPS mode, backend environments, environment name, and region.
New deployment workflow: This guide is intended for routing traffic to new environments. For applications that are already running in production, use the Traffic Distributor Integration workflow.
In the Apps tab, open Dev & Admin Tools or use the search field to find Traffic Distributor. Click Install.
Find Traffic Distributor in the Dev & Admin Tools category.
3Review the solution overview
During the first installation, the platform displays a short description of the package and its main benefits. Select Don’t show this message again to skip this screen during future installations, then click OK.
Review the routing, A/B testing, blue-green deployment, and failover benefits.
4Configure the installation
Complete the interactive installation form and click Install. The platform creates and configures the Traffic Distributor environment automatically.
Set the entry point, balancers, routing method, traffic ratio, HTTPS mode, backends, environment name, and region.
5Confirm successful deployment
After provisioning finishes, a success window appears with links to common Traffic Distributor workflows.
The package has been deployed and is ready to route requests.
Installation Options
Entrypoint
Choose the platform Shared Load Balancer or a dedicated Public IP.
Balancers
Select the number of NGINX instances in the Traffic Distributor topology.
Routing Method
Select Round Robin, Sticky Sessions, or Failover.
Traffic Ratio
Define the relative priority or weight of each backend.
HTTPS
Enable this option when the selected backends serve traffic over HTTPS.
Backends
Select two account environments or manually enter an IP address or domain for a custom host.
Environment
Specify the Traffic Distributor environment domain name.
Display Name
Optionally define the dashboard alias. The default is Traffic Distributor.
Region
Select one of the regions available from the hosting provider.
Endpoint limitation: Endpoint URLs cannot be selected as Traffic Distributor backends because endpoints use external public ports, while traffic between environments on one platform normally uses private ports.
Custom Backend Ports
When the backend service runs on a non-default port, edit the upstream section of the Traffic Distributor NGINX configuration file:
/etc/nginx/nginx-jelastic.conf
Add the required internal container port to the corresponding backend address and define the same port in the backend health-check configuration.
Specify custom internal backend ports in nginx-jelastic.conf and in the health-check parameters.
Resource Requirements
Traffic Distributor resource use mainly depends on the number of incoming requests. The default configuration uses one fixed Cloudlet and can scale vertically up to 16 Cloudlets.
The default resource configuration is generally sufficient even for a large number of simultaneous requests, while automatic vertical scaling allows the balancer to use additional capacity when needed.
Traffic Distributor Reconfiguration
After installation, the platform creates a dedicated environment containing the NGINX load balancer nodes and the Traffic Distributor add-on.
1Open the add-on
Hover over the NGINX layer and click Add-Ons.
Open the Traffic Distributor add-on from the NGINX layer.
2Open configuration
Click Configure in the add-on panel or choose the same option from the menu in the upper-right corner.
Open the Traffic Distributor configuration form.
Reload configuration: Use this option after manually changing Traffic Distributor configuration files. It applies the changes without restarting the node and avoids downtime.
3Adjust the routing settings
Change the entry point, balancer count, routing method, traffic ratio, HTTPS option, or backend hosts. Use Swap backend weights to exchange the traffic-ratio values quickly, then click Apply.
Update routing settings or swap the backend weights.
Configuration Logs
After a configuration update is applied successfully, the dashboard displays a notification with a Show Logs button.
Open the configuration log from the success notification.
The traffic-distributor.log file records the operations performed on the add-on, including timestamps and the current traffic-distribution values.
Review configuration actions, timestamps, and backend distribution values.
The Traffic Distributor log can also be opened manually from the NGINX node’s log files at any time.
