Data Bridges

Data Bridge Name

Region: The region must match your VPC region and should default to the region you are currently in.

Availability Zone ID: The Availability Zone ID identifies the AWS availability zones where this endpoint is available.

Port: The port is used to connect the Data Bridge to Alteryx. The default is 9001.

Download the Bridge Client binary file from the Licensing Portal.

Make the binary executable. The Bridge Client binary must have executable permissions before it can be run.

Import Bridge Client to EC2 with AWS Secret Access:

In AWS, create an EC2 (Amazon Linux AMI) instance that can connect to your private data source and has permission to read or write secrets in AWS Secrets Manager. For more information on how to create an EC2 instance, refer to the AWS documentation Get started with Amazon EC2.

Then, import the Bridge Client into the instance.

Save configuration snippet to a file:

Copy and paste the snippet into a configuration file named bridge-client-config.json, which will be referenced by the Bridge Client.

Example:

{
  "logging": {
    "logLevel": "info", <This can also be "debug">
    "logFormat": "json"
  },
  "bootstrap" : {
    "storageType": "secretsManager"
    "secretName": "<Name of the AWS Secrets Manager secret where the Bridge Client will store its private key. The Bridge Client will create and populate this secret automatically.>"
  },
  "libp2pPort": 9001,
  "libp2pBindIP": "<Private IPv4 address of EC2 Instance that the NLB Target Group Points To On A PrivateLink Endpoint Service.>",
  "resourceFile": "/home/ec2-user/resources.json"
}

Create the resources.json file:

Create a file named resources.json. This file is required for the Bridge Client to start and manage resources at runtime.

The file must contain an empty JSON object ({}) and must not be blank.

Run Bridge Client as a process:

Use systemd to run the Bridge Client as a long-running process.

Example:

[Unit]
Description=Bridge Client

[Service]
ExecStart=/home/ec2-user/bridge-client -c /home/ec2-user/bridge-client-config.json
Restart=always
RestartSec=30s

[Install]
WantedBy=multi-user.target

Start the Bridge Client and enable auto-start with this example command:

sudo systemctl start bridge-client
sudo systemctl enable bridge-client

From the stdout, record the Bridge Client peer ID.

Setup PrivateLink Endpoint Service:

Once the installation is complete, set up the PrivateLink Endpoint Service in your VPC.

Select Next once the Endpoint Service is ready.

The Endpoint Service Name

The Bridge Client peer ID recorded in step 2.

Select a Workspace from the dropdown. Only workspaces with Workspace Execution enabled are shown. Then select Next.

The IAM role is displayed. Copy and paste it to the Allow Principals list in your private VPC. For more information on configuring the AWS IAM Identity Center, refer to Getting started with IAM Identity Center or Configuring IAM Identity Center authentication with the AWS CLI.

Once done, select Next.

A PrivateLink Endpoint has been created. Select Confirm to test the connection.

If the test is successful, continue to Create a New Network Mapping.

Accept the Private Endpoint connection from the Alteryx account.

Name

Description

Host: This is the exact hostname or IP address from your data source connection in Connection Manager or Designer.

Port: The port number configured for your data source.