To connect Looker to [Amazon Aurora MySQL](https://aws.amazon.com/rds/aurora/), follow the instructions found on the documentation page for connecting to [Amazon RDS for MySQL](https://docs.cloud.google.com/looker/docs/2622/db-config-mysql-on-amazon-rds.md.txt).

In addition to the steps in the [Amazon RDS instructions](https://docs.cloud.google.com/looker/docs/2622/db-config-mysql-on-amazon-rds.md.txt), Amazon Aurora may need further setup, depending on your configuration. If you have a redirected read-only endpoint for Amazon Aurora, or if you want to use [persistent derived tables (PDTs)](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#persistent_derived_table), see the following sections.

## Encrypting network traffic

It is a best practice to encrypt network traffic between the Looker application and your database. Consider one of the options that are described on the [Enabling secure database access](https://docs.cloud.google.com/looker/docs/2622/enabling-secure-db-access.md.txt) documentation page.


## Alternate failover and load balancing modes

Amazon Aurora MySQL can be configured to use [alternate failover and load balancing modes](https://mariadb.com/kb/en/about-mariadb-connector-j/#failover-and-load-balancing-modes) to choose the appropriate JDBC connection behavior you want. Check the linked documentation to see how these alternative parameters change the behavior.

You can set the `lookerFailover` parameter in the **Additional JDBC parameters** field to control these modes.

The options can be used to change the JDBC string as follows:

- `lookerFailover=false`: `jdbc:mysql:hostname...`
- `lookerFailover=sequential`: `jdbc:mysql:sequential:hostname...`
  - You can do the same with `lookerFailover=loadbalance`, `lookerFailover=replication`, and `lookerFailover=aurora`
- If `lookerFailover` is not included, the default behavior is: `jdbc:mysql:aurora:hostname...`
- If `cluster-ro` is in the hostname, the default behavior is: `jdbc:mysql:hostname...`

## Configuring Amazon Aurora MySQL for PDTs

In order to use [persistent derived tables (PDTs)](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#persistent_derived_table) with Aurora, you must use MySQL replication, not Amazon Aurora's default replication, which is read-only. You must set the `read_only` parameter to `0` to make the MySQL replica writable, as described in our documentation on [RDS and temporary tables](https://docs.cloud.google.com/looker/docs/2622/db-config-mysql-on-amazon-rds.md.txt#rds_&_temporary_tables).

If you *don't* want to grant write access to the database, you can copy and paste the derived table SQL into the `sql_table_name` parameter of a `view` file as shown here. This creates a subquery that is used at query time:

    view: my_name {
    sql_table_name: (sql_of_derived_table_goes_here) ;;
    }

For more details on Aurora replication, see [the AWS documentation](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Replication.html).


## Creating the Looker connection to your database

In the **Admin** section of Looker, select **Connections** , and then click **Add Connection**.

Fill out the connection details. The majority of the settings are common to most database dialects. See the [Connecting Looker to your database](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt) documentation page for information.

To verify that the connection is successful, click the **Test Connection** button in the **Status details** section at the bottom of the **Connections Settings** page.

If Looker displays **Can Connect** , press **Connect** to create the connection.

Your database connection is then added to the list on the Looker [**Connections**](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-connections.md.txt) **Admin** page.

## Supported JDBC parameters

For Amazon Aurora MySQL, Looker supports the following JDBC parameters in the [**Additional JDBC parameters**](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#additional_jdbc_parameters) field for the connection. See the documentation for your dialect for information on these parameters.

- `allowMultiQueries`
- `autocommit`
- `characterSetResults`
- `clientCertificateKeyStorePassword`
- `clientCertificateKeyStoreUrl`
- `connectionAttributes`
- `connectionCollation`
- `connectionTimeZone`
- `connectTimeout`
- `defaultAuthenticationPlugin`
- `disableSslHostnameVerification`
- `disconnectOnExpiredPasswords`
- `enabledSslCipherSuites`
- `failOverReadOnly`
- `fallbackToSystemTrustStore`
- `forceConnectionTimeZoneToSession`
- `interactiveClient`
- `lookerFailover`
- `maxIdleTime`
- `maxQuerySizeToLog`
- `oldModeNoPrecisionTimestamp`
- `password`
- `passwordCharacterEncoding`
- `permitMysqlScheme`
- `pinGlobalTxToPhysicalConnection`
- `preserveInstants`
- `queryInterceptors`
- `restrictedAuth`
- `rewriteBatchedStatements`
- `socketTimeout`
- `sslMode`
- `tcpKeepAlive`
- `trustCertificateKeyStorePassword`
- `trustCertificateKeyStoreUrl`
- `useCompression`
- `usePipelineAuth`
- `user`
- `useServerPrepStmts`
- `verifyServerCertificate`
- `yearIsDateType`

## Feature support

For Looker to support some features, your database dialect must also support them.

Amazon Aurora MySQL supports the following features as of Looker 26.22:

| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | Yes |
| Symmetric aggregates | Yes |
| Derived tables | Yes |
| Persistent SQL derived tables | Yes |
| Persistent native derived tables | Yes |
| Stable views | Yes |
| Query killing | Yes |
| SQL-based pivots | Yes |
| Time zones | Yes |
| SSL | Yes |
| Subtotals | Yes |
| JDBC additional params | Yes |
| Case-sensitive | No |
| Location type | Yes |
| List type | Yes |
| Percentile | Yes |
| Distinct percentile | Yes |
| SQL Runner Show Processes | Yes |
| SQL Runner Describe Table | Yes |
| SQL Runner Show Indexes | Yes |
| SQL Runner Select 10 | Yes |
| SQL Runner Count | Yes |
| SQL Explain | Yes |
| OAuth 2.0 credentials | No |
| Context comments | Yes |
| Connection pooling | No |
| HLL sketches | No |
| Aggregate awareness | Yes |
| Incremental PDTs | No |
| Milliseconds | Yes |
| Microseconds | Yes |
| Materialized views | No |
| Period-over-period measures | No |
| Approximate count distinct | No |
| In-database analytic models | No |
| Custom calendars | No |