数据桥

数据桥名称

Cloud Provider: AWS

Network Transport: The selected cloud provider determines the private connectivity service. When you select AWS, Alteryx uses AWS PrivateLink. This value is populated automatically and can’t be edited.

区域：该区域必须与您的 VPC 区域匹配，并且应默认为您当前所在的区域。

可用区 ID：可用区 ID 用于标识此端点所在的 AWS 可用区。

端口：该端口用于将数据桥连接到 Alteryx。默认值为 9001。

从许可门户下载 Bridge Client 二进制文件。

使用 AWS 私密访问将 Bridge Client 导入 EC2：

在 AWS 中，使用 Amazon Linux AMI 创建一个 EC2 实例。该实例需能够连接到您的私有数据源，并拥有读取或写入 AWS Secrets Manager 中私密密钥的权限。有关如何创建 EC2 实例的详细信息，请参阅 AWS 文档开始使用 Amazon EC2。

然后，将 Bridge Client 导入到根目录 / 下的 /home/ec2-user 目录中。

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

chmod +x bridge-client

将配置片段保存到文件：

将此代码片段复制并粘贴到 /home/ec2-user 目录下名为 bridge-client-config.json 的配置文件中，该文件将被 Bridge Client 引用。

示例：

{
  "logging": {
    "logLevel": "info",
    "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 the EC2 Instance>",
  "resourceFile": "/home/ec2-user/resources.json"
}

{
  ...
  "bootstrap": {
    "storageType": "aws",
    "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.>",
    "aws": {
      "kmsKeyID": "arn:aws:kms:<region>:<account-id>:key/<key-id>"
    }
  }
  ...
}

{
  "Effect": "Allow",
  "Action": [
    "kms:Decrypt",
    "kms:Encrypt",
    "kms:GenerateDataKey",
    "kms:DescribeKey"
  ],
  "Resource": "arn:aws:kms:<region>:<account-id>:key/<key-id>",
  "Condition": {
    "StringEquals": {
      "kms:ViaService": "secretsmanager.<region>.amazonaws.com"
    }
  }

创建 resources.json 文件：

在 /home/ec2-user 目录中，创建一个名为 resources.json 的文件。Bridge Client 在运行时启动和管理资源需要此文件。

该文件必须包含一个空的 JSON 对象 ({})，且不能为空白。

{}

将 Bridge Client 作为进程运行：

设置 PrivateLink 端点服务：

安装完成后，在 VPC 中设置 PrivateLink 端点服务。

端点服务名称

在第 2 步中记录的 Bridge Client 对等 ID。

从下拉列表中选择一个工作区。仅显示已启用 Workspace Execution 的工作区。然后选择下一步。

系统将显示 IAM 角色。将其复制并粘贴到您私有 VPC 的允许的主体列表中。有关配置 AWS IAM Identity Center 的更多信息，请参阅开始使用 IAM Identity Center 或使用 AWS CLI 配置 IAM Identity Center 身份验证。

完成后，选择下一步。

Go to the PrivateLink service in your AWS Console, then accept the private endpoint connection from the Alteryx account. Make sure the status is green before you continue.

Go to the 3-dot menu next to the workspace entry, then select Test Connection for that workspace. A toast message appears in the lower-left corner and shows the test status and result.

Data Bridge Name

Cloud Provider: Google Cloud, if shown.

Network Transport: The selected cloud provider determines the private connectivity service. When you select GCP, Alteryx uses Private Service Connect. This value is populated automatically and can’t be edited.

Region: The region must match the region where you will deploy the Bridge Client and Private Service Connect service attachment.

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

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

Download the Bridge Client binary file from the Licensing Portal.

Create a Compute Engine VM that can connect to your private data source. The VM should be deployed without a public IP address unless your organization explicitly requires one.

Attach a service account that can access the configured Google Cloud Secret Manager secret.

Make sure the VM has Cloud API access scopes that allow Secret Manager calls.

Import Bridge Client to the VM:

Import the Bridge Client binary to the VM, for example under /etc/ayx/bridge-client directory.

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

sudo chmod +x /etc/ayx/bridge-client/bridge-client

Save configuration snippet to a file:

Copy and paste the snippet into a configuration file named bridge-client-config.json inside of the /etc/ayx/bridge-client directory.

Example:

{
  "logging": {
    "logLevel": "info",
    "logFormat": "json"
  },
  "bootstrap": {
    "storageType": "gcp",
    "secretName": "<Name of the GCP Secret Manager secret where the Bridge Client will store its private key>",
    "gcp": {
      "projectID": "<GCP project ID that owns the Secret Manager secret>"
    }
  },
  "libp2pPort": 9001,
  "peerLibp2pPort": 9001,
  "libp2pBindIP": "<Internal TCP load balancer forwarding rule IP>",
  "resourceFile": "/etc/ayx/bridge-client/resources.json",
  "stateStorage": {
    "type": "file",
    "path": "/etc/ayx/bridge-client/resources.json"
  },
  "rest": {
    "port": "8081"
  }
}

{
  ...
  "bootstrap": {
    "storageType": "gcp",
    "secretName": "<Name of the GCP Secret Manager secret where the Bridge Client will store its private key.>",
    "gcp": {
      "projectID": "<GCP project ID that owns the Secret Manager secret>",
      "kmsKeyID": "projects/<kms-project-id>/locations/<location>/keyRings/<key-ring>/cryptoKeys/<key-name>"
    }
  }
  ...
}

gcloud kms keys add-iam-policy-binding "<key-name>" \
  --project "<kms-project-id>" \
  --location "<location>" \
  --keyring "<key-ring>" \
  --member "serviceAccount:service-<secret-manager-project-number>@gcp-sa-secretmanager.iam.gserviceaccount.com" \
  --role "roles/cloudkms.cryptoKeyEncrypterDecrypter"

Create the resources.json file:

Create a file named resources.json in the /etc/ayx/bridge-client directory. 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:

Set up the internal TCP load balancer:

In Google Cloud, create these resources in the same region as the Bridge Client deployment.

Configure firewall rules to allow:

Create a PSC NAT subnet:

Create a dedicated subnet in the producer VPC with purpose PRIVATE_SERVICE_CONNECT.

The PSC NAT subnet...

Create the Private Service Connect service attachment:

Create a PSC service attachment that points to the internal TCP load balancer forwarding rule.

Use the service attachment URI from the selected Google Cloud region. Example:

projects/PROJECT_ID/regions/REGION_ID/serviceAttachments/bridge-client-psc

For stricter access control, configure the service attachment to accept connections manually and add the Alteryx-provided consumer project, VPC network, or endpoint to the consumer accept list.

Leave PROXY protocol disabled unless Alteryx explicitly instructs you to enable it for Bridge Client.

After the service attachment is created, record the service attachment URI.

The PSC service attachment URI

The Bridge Client peer ID recorded from the Bridge Client logs.

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

Copy the Alteryx-provided GCP consumer identifier. Depending on the configuration, this might be a consumer project, VPC network, or PSC endpoint identifier.

In Google Cloud, update the PSC service attachment consumer accept list or approve the pending connection request.

If the test fails, the setup might not be complete and the remaining steps won’t work.

After the connection test succeeds, you can create a new data source network mapping.