Location Connection for Aurora MySQL
This section describes the connection details required for creating Aurora MySQL location in Fivetran HVR. For information about the pre-requisites, access privileges, and other configuration requirements for creating Aurora MySQL location, see Aurora MySQL Requirements.
HVR uses MariaDB's native Connector/C interface to connect, read, and write data to Aurora MySQL. HVR connects to the Aurora MySQL server using the TCP protocol.
If the managed secrets feature is enabled, option USE TOKEN INSTEAD is displayed in the fields designated for entering secrets.
| Field | Description | Equivalent Location Property |
|---|---|---|
| HOST | Hostname or IP-address of the server on which the Aurora MySQL database is running. Example: 192.168.127.129 | Database_Host |
| PORT | Port number on which the Aurora MySQL database server is expecting connections. Example: 3306 | Database_Port |
| DATABASE | Name of the Aurora MySQL database. Example: mytestdb | Database_Name |
| USER | Username for connecting HVR to the Aurora MySQL database. Example: hvruser | Database_User |
| PASSWORD | Password for the USER. | Database_Password |
Use SSLSince v6.1.5/3 | Enable/disable (one way) SSL. If enabled, HVR authenticates the Auroral MySQL connection by validating the SSL certificate shared by the Aurora MySQL database server. | MySQL_Use_SSL |
MINIMUM TLS VERSIONSince v6.1.5/3 | Minimum TLS protocol version that the client allows for establishing a secure (TLS) connection. Available options are:
| MySQL_SSL_Min_TLS_Version |
CA CERTIFICATE FILESince v6.1.5/3 | Absolute path of the Certificate Authority (CA) certificate file. The value in this field must point to the same certificate used by the server. If a value is specified in this field, the server's Common Name (CN) in its certificate is verified against the hostname used for the connection. If there is a mismatch between the CN and the hostname, the connection will be rejected. | MySQL_CA_Certificate_File |
CLIENT CERTIFICATESince v6.1.5/3 | Absolute path of the client public key certificate file. | MySQL_Client_Pub_Cert_File |
CLIENT PRIVATE KEYSince v6.1.5/3 | The path name of the client private key file. | MySQL_Client_Priv_Key_File |
CRL FILESince v6.1.5/3 | Absolute path to a file containing one or more revoked X.509 certificates to use for TLS. An absolute path must be provided; relative paths are not supported. | MySQL_SSL_CRL_File |
CIPHERSince v6.1.5/3 | Specify the encryption algorithms (ciphers) permitted for establishing a secure connection between HVR and the database server. If this field is left empty, a default set of ciphers will be used. To specify multiple ciphers, list them as comma-separated values. For the connection to succeed, both HVR and the database server must support at least one common cipher from the specified list. The SSL/TLS library will then select the highest-priority cipher compatible with the provided certificate. | MySQL_SSL_Cipher |
SERVER PUBLIC KEYSince v6.1.5/3 | Absolute path to a .pem file containing the client-side copy of the public key required by the server for RSA key pair-based password exchange. This is relevant only for clients using the sha256_password authentication plugin. It is ignored for accounts using other authentication plugins or when RSA-based password exchange is not in use, such as when the client connects to the server via a secure connection. | MySQL_Server_Pub_Key_File |
Staging
HVR supports staging for Aurora MySQL location. For information about the location properties for staging, see Staging for Aurora MySQL.