skip to main content
Welcome to DataDirect Hybrid Data Pipeline : Deployment scenarios : Load balancer deployment : Load balancer configuration : Configuring a cloud load balancer
  

Try Now
Configuring a cloud load balancer
Hybrid Data Pipeline can be deployed on a web service, such as Amazon Web Services or Microsoft Azure, behind a cloud load balancer that supports the WebSocket protocol.
The instructions in this section describe how an Amazon Web Services load balancer must be configured to support Hybrid Data Pipeline. These instructions assume that you have completed the following deployment tasks.
*Created a Virtual Private Cloud (VPC) to host a Hybrid Data Pipeline environment.
*Created AWS instances in the VPC for each node that will be used to support the Hybrid Data Pipeline environment.
*Installed a system database on an AWS node in the VPC for storing user and configuration information.
*Created a file system on a node in the VPC to be used as the key location for shared files.
*Installed the Hybrid Data Pipeline server on each node that will be hosting the service.
*The key location specified during the initial installation must reside on a node in the VPC.
*The system database specified during initial installation is a database you have installed on a separate node in the VPC.
*Created an AWS Application Load Balancer in the VPC to connect to Hybrid Data Pipeline.
The following general steps must be taken to configure routing and listening rules in the AWS Application Load Balancer. The corresponding topics provide detailed instruction for each step.
1. Create a target group for default routing to the Hybrid Data Pipeline service API
2. Create a target group for notifications
3. Create a target group for on-premises access
4. Configure target routing
Once the Application Load Balancer has been configured with listener and target group rules, you can install On-Premises Connectors.
* Create a target group for default routing to the Hybrid Data Pipeline service API
* Create a target group for notifications
* Create a target group for on-premises access
* Configure target routing