Configuring a cloud load balancer with the On-Premises Connector
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. When using an On-Premises Connector, the cloud load balancer must be configured to route requests for on-premises data sources to the correct server nodes.
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 compute instances in the VPC for each node that will be used to support the Hybrid Data Pipeline environment.
Provisioned an RDS database instance to operate as a system database 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 must be the RDS database instance for storing user and configuration information.
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.
Created a Virtual Private Cloud (VPC) to host a Hybrid Data Pipeline environment.
