Puentes de datos

Nombre del puente de datos

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.

Región: la región debe coincidir con la región de tu VPC y debe coincidir de forma predeterminada con la región en la que te encuentres actualmente.

ID de zona de disponibilidad: el ID de zona de disponibilidad identifica las zonas de disponibilidad de AWS en las que está disponible este punto de conexión.

Puerto: el puerto se utiliza para conectar el puente de datos a Alteryx. El valor predeterminado es 9001.

Descarga el archivo binario del cliente Bridge en el Portal de licencias.

Importar cliente Bridge a EC2 con acceso secreto de AWS:

En AWS, crea una instancia de EC2 mediante la AMI de Amazon Linux que pueda conectarse a tu fuente de datos privada y tenga permiso para leer o escribir secretos en AWS Secrets Manager. Para obtener más información sobre cómo crear una instancia EC2, consulta la documentación de AWS Introducción a Amazon EC2.

Luego, importa el cliente Bridge al directorio /home/ec2-user en /.

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

chmod +x bridge-client

Guardar fragmento de configuración en un archivo:

Copia y pega el fragmento en un archivo de configuración llamado bridge-client-config.json dentro del directorio /home/ec2-user, al que el cliente Bridge hará referencia.

Ejemplo:

{
  "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"
    }
  }

Crear el archivo resources.json:

Crea un archivo llamado resources.json en el directorio /home/ec2-user. Este archivo es necesario para que el cliente Bridge inicie y administre recursos en tiempo de ejecución.

El archivo debe contener un objeto JSON vacío ({}) y no debe estar en blanco.

{}

Ejecutar el cliente Bridge como un proceso:

Configurar el servicio de punto de conexión de PrivateLink:

Una vez finalizada la instalación, configura el servicio de punto de conexión de PrivateLink en tu VPC.

El nombre del servicio del punto de conexión

El Id. de par del cliente Bridge se registró en el paso 2.

Selecciona un espacio de trabajo del menú desplegable. Solo se muestran los espacios de trabajo con la ejecución en el espacio de trabajo habilitada. A continuación, selecciona Siguiente.

Se muestra el rol de IAM. Cópialo y pégalo en la lista Permitir entidades en tu VPC privada. Para obtener más información sobre cómo configurar el centro de identidad de AWS IAM, consulta Introducción al centro de identidad de IAM o Configuración de la autenticación del centro de identidad de IAM con AWS CLI.

Una vez hecho esto, selecciona Siguiente.

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.