MySQL Requirements
This section describes the requirements, access privileges, and other features of Fivetran HVR when using MySQL for replication.
Supported Platforms
Supported Capabilities
Data Management
Learn how HVR maps data types between source and target DBMSes or file systems on the Data Type Mapping page. For the list of supported MySQL data types and their mapping, see Data Type Mapping for MySQL.
Understand the character encodings HVR supports for MySQL on the Supported Character Encodings page.
Fivetran provides additional solutions for replicating data from MySQL. For more information, see section MySQL in Databases.
Connecting to Amazon RDS for MySQL
To enable the HVR capture or integrate process to connect to Amazon RDS for MySQL, you must allow inbound traffic on the database listener port to the system running the HVR process. If an HVR Agent is in place, then communication must be enabled for the system where the HVR Agent is running. When directly connected from an HVR Hub Server, the connection must be allowed for the HVR Hub Server. If the HVR system connecting to Amazon RDS for MySQL runs in the same VPC as Amazon RDS for MySQL, you can use the internal rather than public IP address for the service to allow access. It is recommended to restrict access to only the HVR system that requires access, rather than allowing broader or public access.
The default database listener port that must be opened for TCP/IP connection is 3306.
NOTE: The port may have been changed from the default by an administrator.
Using Authentication Plugins
HVR supports using MariaDB authentication plugins for user authentication. For more information about authentication plugins, refer to the Authentication Plugins section in the MariaDB documentation. To use authentication plugins installed in a custom directory, you must define the environment variable MARIADB_PLUGIN_DIR. You can define this environment variable using the action Environment with parameters Name=MARIADB_PLUGIN_DIR and Value=path_to_directory.