Amazon Aurora (MySQL)

Hevo can replicate tables from your Aurora database.

Pipeline Modes

Pipeline mode will define how you want Hevo to read your data from Aurora source.

  • Table: In this mode, your tables will be polled individually at a fixed frequency. You can use this mode when you are looking to fetch data from multiple tables in your database and you would like to have control over ingestion for every table individually.
  • Custom SQL: If you are looking to fetch data in a different structure than how it is stored in your source tables, you can use this mode. It will allow you to write a custom query and data will be polled using that query at a fixed frequency.
  • BinLog: Data will be polled using Aurora’s BinLog in this mode. This mode is useful when you are looking to replicate the complete database as it is. This mode is very efficient in replicating but leaves you with less control and manageability over data ingestion. A few pointers on setting up the binary logs may be found here.

Connection Settings

Provide your Aurora database connection details on Aurora Connection Settings page. You will have the following options in the connection details block:

  • Source Name - A unique name for this source
  • Aurora Host - Aurora host’s IP address or DNS
  • Aurora Port - The port on which your Aurora server is listening for connections (default is 3306)
  • Database User - The read-only user that can read the tables in your database.
  • Database Password - Password for the read-only user
  • Database Name - The database that you wish to replicate
  • If you want to connect to Hevo using an SSH tunnel, check Connecting Through SSH. Else, you will have to whitelist Hevo’s IP addresses as listed here.

Job Settings

Job Settings may be required if Hevo needs your inputs to query data from your database. Each Job listed represents a table in your database. Each Job can be configured with a Query Mode. You can read more about Query Modes.

Last updated on 25 Aug 2020