Configuring target endpoints Elasticsearch

Data nodes: Click to add a new data node. For each node, specify:

• Host: IP address or FQDN of the host with the DATA role you want to connect to.

• Port: Port number Data Transfer will use for connections to the DATA host.

CA certificate: Upload the certificate file or add its contents as text if transmitted data must be encrypted, for example, to meet PCI DSS requirements.

Subnet ID: Select or create a subnet in the desired availability zone.

If the value in this field is specified for both endpoints, both subnets must be hosted in the same availability zone.

User: Specify the username Data Transfer will use to connect to the cluster.

Password: Enter the user password to the cluster.

Security groups: Select the cloud network to host the endpoint and security groups for network traffic.

This will let you apply the specified security group rules to the VMs and clusters in the selected network without changing the settings of these VMs and clusters. For more information, see Network in Data Transfer.

Cleanup policy: Select a way to clean up data in the target database before the transfer:

• Don't cleanup: Select this option if you are only going to do replication without copying data.

• Drop: Fully delete tables included in the transfer (used by default).

  Use this option so that the latest version of the table schema is always transferred to the target database from the source whenever the transfer is activated.

Sanitize documents keys: Use this option to automatically replace keys that are not valid for Elasticsearch in the target fields.

The auto replacement rules are as follows:

• Empty keys or keys that consist of spaces and periods are replaced with underscores: "", " ", "." → "_".
• Periods at the beginning and end of a key are removed: "somekey.", ".somekey" → "somekey".
• If there are two periods in a row or there is a space between them, the entire fragment is replaced with a period: " some . . key" → " some . key".

E.g., ". s o m e ..incorrect....key. . . " → " s o m e .incorrect.key".