Launch the CData Sync AMI on Amazon Web Services



CData Sync is a lightweight web application that helps you easily replicate data into any data warehouse in minutes. The CData Sync Amazon Machine Instance (AMI) comes as a Linux-based instance with CData Sync pre-configured and ready to run, with no additional configuration necessary.

The AMI can be found in the AWS Marketplace as CData Sync. You can launch a new instance of CData Sync from the Amazon AMI in three simple steps.

  1. Subscribe to the AMI, and accept the Terms and Conditions. Once you are subscribed, you can launch a new instance of CData Sync.

  2. Configure the instance-type, instance details, volume, tags, and security group. CData Sync runs on the default HTTPS port (443); ensure this port is accessible from the IP address you connect to CData Sync. Next, create a new key-pair or select an existing one.

  3. Once the instance has launched, it will be listed in your instances running EC2. You can then access CData Sync in your browser at the URL:

    https://<instance_public_dns>

    To log in, the default username is 'admin,' and the password is the instance's randomly generated Instance-ID, which you can find from the EC2 management console.

You can now connect to your data sources, secure connections with SSL, and standard authentication methods. See the "Getting Started" chapter in the help for a guide to setting the required connection properties and setting up access control.

Advanced configuration

The CData Sync AMI works out-of-the-box without additional configuration. However, advanced users can customize CData Sync to manage replications with more precision.

Access to the Instance via SSH

Connecting to the EC2 instance via SSH can be useful for advanced configuration of the service. The CData Sync AMI is based on a standard CentOS 7 VM, and the main user is centos. You can connect to it via SSH using the key-pair selected when launching the instance:

ssh -i my_key_pair.pem centos@<instance_public_dns>

Stop, Start, or Restart the CData Sync service

CData Sync runs using Jetty. Once connected to the instance, use systemctl to manage the Jetty service:

sudo systemctl restart jetty
sudo systemctl stop jetty
sudo systemctl start jetty

Connect to Additional Data Sources

CData Sync supports several replication sources and destinations out of the box, but there are many additional connectors available. To add a new source or destination in the CData Sync instance, download and install the corresponding Java Sync Connector.

The CData Sync AMI is licensed for a base number of connections. If you would like to add more connections, contact our sales team.

Copy the JAR file of the connector on the instance via SSH using your key-pair. The connector needs to be installed in the directory /opt/jetty/lib/ext/. For example, you can use the scp command:

scp -i my_key_pair.pem cdata.jdbc.salesforce.jar centos@<instance_public_dns>:/opt/jetty/lib/ext/

After copying the JAR file, restart the jetty service:

sudo systemctl restart jetty

Install a Trusted Certificate

By default, the CData Sync AMI generates a new self-signed certificate upon creation, preventing any two AMIs from sharing the same certificate. However, not all client applications accept self-signed certificates. To get around this, you can replace the default certificate with a trusted one.

First, obtain a trusted certificate from a certificate provider. This certificate must match the public URL provided by AWS.

In the AMI, the Jetty web-container handles the SSL configuration. Import your certificate as a new keystore file in your EC2 instance. In the file /opt/datasync/etc/ssl.xml, modify the lines referencing the path to the current certificate keystore with the new path and password:

<Set name='KeyStorePath'><Property name='jetty.base' default='.'/>/etc/my_trusted_keystore</Set>
<Set name='KeyStorePassword'>my_keystore_password</Set>

Note that the keystore path is a relative path starting from the Jetty Base directory (/opt/datasync). After saving the modifications to this file, restart the Jetty service for these changes to take effect.