> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon Aurora Connector

> Connect TextQL to your Amazon Aurora database

## Overview

This guide walks you through connecting TextQL to your Amazon Aurora database. Aurora supports both MySQL and PostgreSQL engines, and this guide covers both.

## Prerequisites

To connect TextQL with your Amazon Aurora database, you will need:

* **Host URL** (SQL endpoint) and **Port** (default: 3306 for MySQL, 5432 for PostgreSQL)
* **Username** and **Password**
* **Database** name
* **Dialect** (MySQL or PostgreSQL)

## Gathering Connection Details from AWS

### Step 1: Get Credentials from AWS Secrets Manager

1. Navigate to **AWS Management Console** and search for **Secrets Manager**
2. Find your database secret (named like `rds!db-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`)
3. Click the secret and then click **Retrieve secret value**
4. Copy the **username** and **password** values

### Step 2: Get Host and Port from RDS Console

1. Go to **AWS RDS Console** and click **Databases** in the left sidebar
2. Click on your Aurora database instance
3. Click the **Connectivity & security** tab
4. Under **Endpoint & port** section, copy the **endpoint URL** and **port number**

### Step 3: Identify Database Engine

1. On the database details page, click the **Configuration** tab
2. Note the **Engine type** (e.g., MySQL Community 8.0.43 or PostgreSQL)
3. This determines which **Dialect** to select in TextQL

### Example Connection Details

```
Host: your-database.cluster-xxxxx.us-east-1.rds.amazonaws.com
Port: 3306
Username: admin
Password: (from Secrets Manager)
Dialect: MySQL
Database: mydb
```

## Creating the Connector in TextQL

### Step 1: Navigate to Connectors Page

1. Go to the [TextQL Connectors Page](https://app.textql.com/connectors)
2. Click **New Connector**

### Step 2: Select Amazon Aurora

Select **Amazon Aurora** from the available connectors to open the configuration form.

### Step 3: Enter Connection Details

The form requires the following information:

| Field | Description | Example |
| - | - | - |
| **Connector Name** | A descriptive name to identify this connection | `My Aurora Cluster` |
| **Host URL** | The endpoint URL from RDS console | `aurora-cluster.cluster-xxxxx.us-east-1.rds.amazonaws.com` |
| **Port** | Port number (3306 for MySQL, 5432 for PostgreSQL) | `3306` |
| **Dialect** | Select MySQL or PostgreSQL based on engine type | `MySQL` |
| **Username** | Your database username | `admin` |
| **Password** | Your database password from Secrets Manager | `••••••••` |
| **Database** | The name of the database to connect to | `ecommerce` |
| **Schema** | (Optional) Specific schema within your database | `public` |

### Step 4: Test and Create

1. Click **Test Connection** to verify your credentials and network access
2. Once the test succeeds, click **Create Connector** to save the connection

## Troubleshooting

### Connection Fails

**Verify the following:**

* Credentials are correct and match what's configured in AWS
* Aurora cluster is running and accessible
* Using the correct endpoint (dedicated vs. serverless)

> [!NOTE]
>
> Having trouble connecting? See the [Network Configuration Guide](https://docs.textql.com/core/datasources/databases/network-configuration.md) for firewall and IP whitelisting setup.

### Certificate Errors

TextQL always connects to Aurora over TLS and checks the server certificate against the Amazon RDS certificate authorities and your endpoint name, whether or not **Enable SSL** is on. Someone who redirects the endpoint's DNS cannot intercept the connection or its credentials.

A connection through a custom DNS name or an IP address fails, because the Aurora certificate only lists the AWS endpoint names. Use the cluster or instance endpoint from the RDS console, or turn on **Skip TLS certificate verification** to connect without the check.

### Authentication Errors

**Check:**

* Username and password from Secrets Manager are correct
* User has appropriate database permissions
* Password hasn't expired

### Timeout Errors

**Possible causes:**

* Security group rules not configured correctly
* VPC configuration blocking external access
* Aurora cluster is stopped or paused
* Network connectivity issues

## What's Next

Once your Aurora connector is set up, you can:

* Ask Ana natural language questions about your data
* Generate SQL queries and visualizations
* Create reports and dashboards
* Share insights with your team


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.