Continuent Documentation

Search:
Page in Other Manuals

6.1. Deploying the Replicator using the AWS Marketplace AMI

If you have an AWS account, you can take advantage of a pre-built EC2 host, complete with all necessary host pre-requisites in place, launched from a Marketplace AMI.

Upon launch, a wizard will start and prompt you for a number of credentials to build a default configuration for Tungsten Replicator

The AMI can be configured to be an extractor and/or an applier for a number of pre-configured topologies, these are as follows:

Source Databases

  • MySQL hosted on another EC2 instance

  • MySQL hosted on the same EC2 host launched from the AMI (See Note 1)

  • Amazon RDS

  • Amazon Aurora

  • MySQL hosted on remote host, non-AWS host (See Note 2)

  • Google Cloud SQL (See Note 2)

  • Microsoft Azure (See Note 2)

Target Databases

  • MySQL hosted on another EC2 instance

  • MySQL hosted on the same EC2 host launched from the AMI (See Note 1)

  • Amazon RDS

  • Amazon Aurora

  • MySQL hosted on remote host, non-AWS host (See Note 2)

  • Google Cloud SQL (See Note 2)

  • Microsoft Azure (See Note 2)

  • Amazon Redshift

  • HP Vertica (Local or Remote) (See Note 1)

  • PostgreSQL (Local, Remote or RDS) (See Note 1)

  • Apache Kafka (Local or Remote) (See Note 1)

Note 1 : Upon launch, the AMI does NOT include the required binaries for a locally hosted database instance. For a local install for either the extractor or the applier, this will need to be configured manually beforehand.

Note 2 : For any non-AWS hosted instance, ensure the appropriate inbound and outbound security rules are in place to allow WAN Communication