Amazon Aurora MySQL

Last updated on Oct 18, 2023

Hevo can load data from any of your Pipelines into an Amazon Aurora MySQL database. Follow the steps in this page to configure Amazon Aurora MySQL as a Destination.

We do not recommend using an Amazon Aurora MySQL Destination for building your production Pipelines. It can perform poorly even for low volumes of data. If you run into performance issues, these may be unresolvable, and you will have to migrate to a different Destination. Read Limitations of using MySQL as a Destination.

Destination Considerations

  • You must disable any foreign keys defined in the target tables. Foreign keys do not allow data to be loaded until the reference table has a corresponding key defined.


  • Hevo replicates a maximum of 4096 columns to each Amazon Aurora MySQL table, of which, six are Hevo-reserved metadata columns used during data replication. Therefore, your Pipeline can replicate up to 4090 (4096-6) columns for each table.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Apr-25-2023 2.12 Updated section, Configure Amazon Aurora MySQL Connection Settings to add information that you must specify all fields to create a Pipeline.
Sep-07-2022 NA Added the following sections:
- Prerequisites,
- Whitelist Hevo’s IP Addresses,
- Create a Database User and Grant Privileges,
- Retrieve the Hostname and Port Number.
Feb-21-2022 1.82 Updated section, Configure Amazon Aurora MySQL Connection Settings to provide support for SSL in Amazon Aurora MySQL as a Destination.
Jul-12-2021 NA Added section, Destination Considerations.

Tell us what went wrong