> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/amazon-aurora.md).

# Amazon Aurora

This article outlines the integration with the Amazon Aurora connector, enabling metadata extraction through features such as crawling, profiling, sample profiling, Query Sheet, data preview, data quality, and lineage building (both automatic and manual). It supports Amazon Aurora MySQL and Amazon Aurora PostgreSQL databases.

The connector establishes connectivity to Amazon Aurora using the JDBC driver. Based on the selected repository type, it connects to either Amazon Aurora MySQL or Amazon Aurora PostgreSQL to retrieve metadata and build lineage.

<img src="/files/GaxtkAXbt2pesSRVpBjB" alt="" height="372" width="624">

## Overview

### Connector Details

<table data-header-hidden><thead><tr><th width="451"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>RDBMS</td></tr><tr><td>OvalEdge Release Supported</td><td>Release7.x and later</td></tr><tr><td><p>Connectivity</p><p>[How the connection is established with Amazon Aurora]</p></td><td>JDBC Driver</td></tr><tr><td>Verified AWS Aurora Versions</td><td><p><strong>Aurora MySQL</strong>: 5.7.12 and later</p><p><strong>Aurora PostgreSQL</strong>: Compatible with AWS Aurora PostgreSQL engine versions</p></td></tr></tbody></table>

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Profiling                                    |       ✅      |
| Sample Profiling                             |       ✅      |
| Query Sheet                                  |       ✅      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ✅      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

### Metadata Mapping

The following tables describe the metadata objects and attributes extracted from Amazon Aurora MySQL and Amazon Aurora PostgreSQL during crawling, along with their corresponding mappings to OvalEdge assets, attributes, categories, and object types.

#### Amazon Aurora MySQL Metadata Mapping

<table><thead><tr><th width="150">Amazon Aurora Object</th><th width="266">Amazon Aurora Attribute</th><th width="171">OvalEdge Attribute</th><th width="175">OvalEdge Category</th><th width="175">OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>SCHEMA_NAME</td><td>Schema</td><td>Databases</td><td>Schema</td></tr><tr><td>Schema</td><td>Schema comment</td><td>-</td><td>-</td><td>-</td></tr><tr><td>Table</td><td>TABLE_NAME</td><td>Table</td><td>Tables</td><td>table</td></tr><tr><td>Table</td><td>TABLE_TYPE</td><td>Type</td><td>Tables</td><td>table</td></tr><tr><td>Table</td><td>table_comment</td><td>Source Description</td><td>Descriptions</td><td>Source Description</td></tr><tr><td>Columns</td><td>COLUMN_NAME</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>data_type</td><td>Column Type</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>COLUMN_COMMENT</td><td>Source Description</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>ordinal_position</td><td>Column Position</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>character_maximum_length / numeric_precision</td><td>Data Type Size</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>COLUMN_KEY (PRI / MUL)</td><td>Keys</td><td>Table Columns</td><td>-</td></tr><tr><td>Views</td><td>TABLE_NAME</td><td>View</td><td>Tables</td><td>view</td></tr><tr><td>Views</td><td>VIEW_DEFINITION</td><td>View Query</td><td>Views</td><td>view</td></tr><tr><td>Procedures</td><td>ROUTINE_NAME</td><td>Name</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>ROUTINE_DEFINITION</td><td>Procedure</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>ROUTINE_TYPE = PROCEDURE</td><td>Type</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr><tr><td>Functions</td><td>ROUTINE_NAME</td><td>Name</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>ROUTINE_DEFINITION</td><td>Function</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>ROUTINE_TYPE = FUNCTION</td><td>Type</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr><tr><td>Triggers</td><td>trigger_name</td><td>Name</td><td>Triggers</td><td>-</td></tr><tr><td>Triggers</td><td>trigger_code (full CREATE TRIGGER)</td><td>Trigger Data</td><td>Triggers</td><td>-</td></tr><tr><td>Triggers</td><td>action_timing</td><td>Type</td><td>Triggers</td><td>-</td></tr><tr><td>Keys</td><td>CONSTRAINT_NAME, REFERENCED_TABLE_NAME, REFERENCED_COLUMN_NAME</td><td>Keys / Relationships</td><td>Table Columns</td><td>-</td></tr><tr><td>Indexes</td><td>INDEX_NAME</td><td>Index</td><td>Indexes</td><td>Index</td></tr><tr><td>Indexes</td><td>NON_UNIQUE</td><td>Yes / No</td><td>Indexes</td><td>Index</td></tr></tbody></table>

#### Amazon Aurora PostgreSQL Metadata Mapping

<table><thead><tr><th width="140">Amazon Aurora Object</th><th width="282">Amazon Aurora Attribute</th><th>OvalEdge Attribute</th><th>OvalEdge Category</th><th>OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>SCHEMA_NAME</td><td>Schema</td><td>Databases</td><td>Schema</td></tr><tr><td>Schema</td><td>obj_description (pg_namespace)</td><td>Source Description</td><td>Databases</td><td>Schema</td></tr><tr><td>Table</td><td>TABLE_NAME</td><td>Table</td><td>Tables</td><td>table</td></tr><tr><td>Table</td><td>TABLE_TYPE</td><td>Type</td><td>Tables</td><td>table</td></tr><tr><td>Table</td><td>pg_description (pg_class)</td><td>Source Description</td><td>Descriptions</td><td>Source Description</td></tr><tr><td>Table</td><td>matviewname (pg_matviews)</td><td>Table</td><td>Tables</td><td>materialized view</td></tr><tr><td>Columns</td><td>COLUMN_NAME</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>data_type</td><td>Column Type</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>pg_description (column comment)</td><td>Source Description</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>ordinal_position</td><td>Column Position</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>character_maximum_length / numeric_precision</td><td>Data Type Size</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>constraint_type (PRIMARY KEY / FOREIGN KEY)</td><td>Keys</td><td>Table Columns</td><td>-</td></tr><tr><td>Views</td><td>TABLE_NAME</td><td>View</td><td>Tables</td><td>view</td></tr><tr><td>Views</td><td>VIEW_DEFINITION</td><td>View Query</td><td>Views</td><td>view</td></tr><tr><td>Views</td><td>definition (pg_matviews)</td><td>View Query</td><td>Views</td><td>Materialized View</td></tr><tr><td>Procedures</td><td>proname</td><td>Name</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>pg_get_functiondef (prokind = 'p')</td><td>Procedure</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr><tr><td>Functions</td><td>proname</td><td>Name</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>pg_get_functiondef (prokind = 'f')</td><td>Function</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr><tr><td>Triggers</td><td>trigger_name</td><td>Name</td><td>Triggers</td><td>-</td></tr><tr><td>Triggers</td><td>action_statement</td><td>Trigger Data</td><td>Triggers</td><td>-</td></tr><tr><td>Triggers</td><td>-</td><td>Type</td><td>Triggers</td><td>-</td></tr><tr><td>Keys</td><td>constraint_name, REFERENCED_TABLE_NAME, REFERENCED_COLUMN_NAME</td><td>Keys / Relationships</td><td>Table Columns</td><td>-</td></tr><tr><td>Indexes</td><td>index_name (pg_index)</td><td>Index</td><td>Indexes</td><td>Index</td></tr><tr><td>Indexes</td><td>indisunique</td><td>Yes / No</td><td>Indexes</td><td>Index</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

#### **Whitelisting Ports**

Make sure that the appropriate inbound database port is whitelisted to enable successful connectivity with Amazon Aurora.

{% hint style="warning" %}
The default port depends on the Amazon Aurora database:

* 3306 for Amazon Aurora MySQL
* 5432 for Amazon Aurora PostgreSQL

If a non-default port is configured, specify the custom port during connection setup, ensure the port is whitelisted, and verify that communication between the system and the Amazon Aurora database is successfully established.
{% endhint %}

#### **External Supporting Files**

{% hint style="info" %}
The required external JAR files are included as part of the OvalEdge installation artifacts. For driver installation and configuration details, refer to the [Connector Drivers Setup Guide](https://docs.ovaledge.com/connectors/additional-requirements/connector-drivers-setup-guide). Please contact the OvalEdge Team for assistance related to the driver files and configuration setup.
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
**👨‍💻 Who can provide these permissions?** The Amazon Aurora administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

**Amazon Aurora MySQL - Access Permissions**

<table><thead><tr><th width="194">Operations</th><th width="198">Objects</th><th width="227">Sys Tables</th><th width="186">Access Permissions</th></tr></thead><tbody><tr><td>Crawling &#x26; Profiling</td><td>Schemas</td><td>INFORMATION_SCHEMA.SCHEMATA</td><td>SELECT</td></tr><tr><td>Crawling &#x26; Profiling</td><td>Tables</td><td>INFORMATION_SCHEMA.TABLES</td><td>SELECT</td></tr><tr><td>Crawling &#x26; Profiling</td><td>Table Columns</td><td>INFORMATION_SCHEMA.COLUMNS</td><td>SELECT</td></tr><tr><td>Crawling, Profiling &#x26; Lineage</td><td>Views</td><td>INFORMATION_SCHEMA.VIEWS</td><td>SELECT, SHOW VIEW</td></tr><tr><td>Crawling &#x26; Lineage</td><td>Functions / Stored Procedures</td><td>INFORMATION_SCHEMA.ROUTINES</td><td>SELECT</td></tr><tr><td>Crawling &#x26; Lineage</td><td>Triggers</td><td>INFORMATION_SCHEMA.TRIGGERS</td><td>SELECT</td></tr><tr><td>Crawling</td><td>Relationships</td><td>INFORMATION_SCHEMA.KEY_COLUMN_USAGE</td><td>SELECT</td></tr><tr><td>Crawling</td><td>Indexes</td><td>INFORMATION_SCHEMA.STATISTICS</td><td>SELECT</td></tr><tr><td>Crawling (Optional – RDAM)</td><td>User / Schema Permissions</td><td>INFORMATION_SCHEMA.SCHEMA_PRIVILEGES</td><td>SELECT</td></tr><tr><td>Crawling (Optional – RDAM)</td><td>User / Table Permissions</td><td>INFORMATION_SCHEMA.TABLE_PRIVILEGES</td><td>SELECT</td></tr><tr><td>Lineage (Optional – Query Log Crawl)</td><td>Query Logs</td><td>mysql.general_log</td><td>SELECT</td></tr><tr><td>Profiling / Data Preview / Query Sheet</td><td>Tables / Views</td><td>Database Tables and Views</td><td>SELECT</td></tr></tbody></table>

**Amazon Aurora PostgreSQL - Access Permissions**

| Operations                               | Objects                       | Sys Tables                                                                                                                                     | Access Permissions                   |
| ---------------------------------------- | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| Crawling & Profiling                     | Schemas                       | information\_schema.schemata / pg\_namespace                                                                                                   | SELECT on catalog views              |
| Crawling & Profiling                     | Tables                        | information\_schema.tables / pg\_class                                                                                                         | SELECT on catalog views              |
| Crawling & Profiling                     | Table Columns                 | information\_schema.columns                                                                                                                    | SELECT on catalog views              |
| Crawling, Profiling & Lineage            | Views                         | pg\_views / information\_schema.views                                                                                                          | SELECT on catalog views              |
| Crawling, Profiling & Lineage (Optional) | Materialized Views            | pg\_matviews                                                                                                                                   | SELECT on catalog views              |
| Crawling & Lineage                       | Functions / Stored Procedures | pg\_proc + pg\_get\_functiondef()                                                                                                              | SELECT on catalog views              |
| Crawling & Lineage                       | Triggers                      | pg\_trigger + pg\_get\_triggerdef()                                                                                                            | SELECT on catalog views              |
| Crawling                                 | Relationships                 | information\_schema.table\_constraints, information\_schema.key\_column\_usage, information\_schema.constraint\_column\_usage / pg\_constraint | SELECT on catalog views              |
| Crawling (Optional)                      | Indexes                       | pg\_indexes / pg\_index                                                                                                                        | SELECT on catalog views              |
| Crawling (Optional – RDAM)               | User / Schema Permissions     | information\_schema.schema\_privileges                                                                                                         | SELECT on catalog views              |
| Crawling (Optional – RDAM)               | User / Table Permissions      | information\_schema.role\_table\_grants                                                                                                        | SELECT on catalog views              |
| Lineage (Optional – Query Statistics)    | Query Statistics              | pg\_stat\_statements                                                                                                                           | pg\_read\_all\_stats (or equivalent) |
| Lineage (Optional – Server Logs)         | Server Logs                   | Aurora PostgreSQL External Logs                                                                                                                | N/A                                  |

{% hint style="info" %}

* The connector establishes connectivity to Amazon Aurora using the native JDBC driver. The required JDBC driver is bundled with OvalEdge by default and supports both Amazon Aurora MySQL and Amazon Aurora PostgreSQL.
* Metadata crawling retrieves schemas, tables, columns, relationships, indexes, views, functions, stored procedures, and triggers from the corresponding system catalog objects. Optional RDAM metadata includes schema- and table-level privileges.
* **Amazon Aurora MySQL**: View metadata requires the SHOW VIEW privilege in addition to SELECT. Query log-based lineage is supported through mysql.general\_log and requires the general query log to be enabled.
* **Amazon Aurora PostgreSQL**: View, function, and trigger definitions are retrieved from PostgreSQL system catalog views. Query-based lineage can use pg\_stat\_statements when the extension is enabled, while server logs are available through Aurora log export mechanisms such as CloudWatch.
* Profiling, Data Preview, and Query Sheet operations require SELECT permission on the target tables and views.
  {% endhint %}

### Connection Configuration Steps

{% hint style="warning" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log into **OvalEdge**, go to **Administration** > **Connectors**, click **+ (New Connector)**, search for **Amazon Aurora**, and enter the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="220">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "AWSAURORA" is displayed as the selected connector type.</td></tr><tr><td>AWS Aurora Repository type* </td><td><p>Select the Amazon Aurora repository type for the connection.</p><ul><li>MYSQL</li><li>POSTGRES</li></ul></td></tr></tbody></table>

{% tabs %}
{% tab title="MYSQL" %}

<table><thead><tr><th width="191">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Authentication* </td><td><p>Select the authentication method used to establish the connection with the Amazon Aurora database.</p><ul><li>UserId &#x26; Password Authentication</li><li>Azure Entra ID Authentication</li></ul></td></tr><tr><td>SSL Enabled* </td><td>Select True to establish a secure SSL-encrypted connection to the Amazon Aurora database, or False to connect without SSL. Ensure the database is configured to support the selected option.</td></tr><tr><td>Use SSH Tunnel* </td><td>Select True to connect through an SSH tunnel when the Amazon Aurora database is not directly accessible over the network. Select False for a direct database connection. </td></tr><tr><td>SSH Host/IP* </td><td><p>Enter the hostname or IP address of the SSH server used to establish the secure tunnel to the Amazon Aurora database. </p><p><strong>Note</strong>: This field is displayed only when Use SSH Tunnel is set to True. </p></td></tr><tr><td>SSH Port* </td><td><p>Enter the port number configured for the SSH server to establish the SSH tunnel. </p><p><strong>Note</strong>: This field is displayed only when Use SSH Tunnel is set to True. </p></td></tr><tr><td>SSH User Name* </td><td><p>Enter the username (SSH Tunnel) used to authenticate with the SSH server.</p><p><strong>Note</strong>: This field is displayed only when Use SSH Tunnel is set to True. </p></td></tr><tr><td>SSH Password* </td><td>Enter the password associated with the SSH user account.<br><strong>Note</strong>: This field is displayed only when Use SSH Tunnel is set to True. </td></tr><tr><td>Local Port* </td><td>Enter the local port number used for SSH port forwarding between the local machine and the Amazon Aurora database. Ensure the specified port is available on the local system.<br><strong>Note</strong>: This field is displayed only when Use SSH Tunnel is set to True. </td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><ul><li>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</li><li>Select the checkbox for Data Quality Add-On to identify data quality issues using data quality rules and anomaly detection.</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Amazon Aurora connection              </p><p>(Example: "Amazon Aurora_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</p></td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Server*</td><td>Enter the Amazon Aurora database endpoint (host name) or IP address of the target database server (Example: aurora-xxxxxxxx.us-east-1.rds.amazonaws.com  or 192.xxx.xx.20).</td></tr><tr><td>Port*</td><td>By default, the port number for Aurora MySQL, "3306" is auto-populated. If required, the port number can be modified as per the custom port number that is configured for Amazon Aurora.</td></tr><tr><td>Database*</td><td>Enter the name of the target Amazon Aurora database to which the connector will establish the connection. Ensure the specified database is accessible by the configured service account.</td></tr><tr><td>Driver*</td><td>By default, the driver detail is automatically populated based on the selected repository type and cannot be modified (Aurora MySQL: com.mysql.cj.jdbc.Driver).</td></tr><tr><td>Username*</td><td>Enter the service account username with the required permissions to access Amazon Aurora metadata and data. Ensure that the account has the required permissions to access the database metadata and data.</td></tr><tr><td>Password*</td><td><p>Enter the password associated with the configured service account user.</p><p>Note: This field appear only if the authentication field is selected as “UserId &#x26; Password Authentication”.</p></td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Oracle database:</p><ul><li>Automatic mode: The system generates a connection string based on the provided credentials.</li><li>Manual mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to the database name.</p></td></tr><tr><td>Plugin Server</td><td>Enter the server’s name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>
{% endtab %}

{% tab title="POSTGRES" %}

<table><thead><tr><th width="190">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><ul><li>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</li><li>Select the checkbox for Data Quality Add-On to identify data quality issues using data quality rules and anomaly detection.</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Amazon Aurora connection              </p><p>(Example: "Amazon Aurora_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</p></td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Server*</td><td>Enter the Amazon Aurora database endpoint (host name) or IP address of the target database server (Example: aurora-xxxxxxxx.us-east-1.rds.amazonaws.com  or 192.xxx.xx.20).</td></tr><tr><td>Port*</td><td>By default, the port number for Aurora PostgreSQL, "5432" is auto-populated. If required, the port number can be modified as per the custom port number that is configured for Amazon Aurora.</td></tr><tr><td>Database*</td><td>Enter the name of the target Amazon Aurora database to which the connector will establish the connection. Ensure the specified database is accessible by the configured service account.</td></tr><tr><td>Driver*</td><td>By default, the driver detail is automatically populated based on the selected repository type and cannot be modified (POSTGRES: org.postgresql.Driver).</td></tr><tr><td>Username*</td><td>Enter the service account username with the required permissions to access Amazon Aurora metadata and data. Ensure that the account has the required permissions to access the database metadata and data.</td></tr><tr><td>Password*</td><td>Enter the password associated with the configured service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Oracle database:</p><ul><li><strong>Automatic mode</strong>: The system generates a connection string based on the provided credentials.</li><li><strong>Manual mode</strong>: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to the database name.</p></td></tr><tr><td>Plugin Server</td><td>Enter the server’s name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the drop-down list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="220"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="220"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl/Profile

{% hint style="warning" %}
To perform crawl and profile operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling and profiling.

1. Navigate to the Connectors page and click **Crawl/Profile**.
2. Select the schemas to crawl.
3. The **Crawl** option is selected by default. To perform both operations, select the **Crawl &** **Profile** radio button.
4. Click **Run** to collect metadata from the connected source and load it into the **Data Catalog**.
5. After a successful crawl, the information appears in the **Data Catalog** > **Databases** tab.

The **Schedule** checkbox allows automated crawling for a selected timeframe, from a minute to a year.

1. Click the **Schedule** checkbox to enable the Select Period drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the selected operation (**Crawl** or **Crawl & Profile**) at the scheduled time.

### Other Operations

The Connectors page provides a centralized view of all configured connectors and their health status.

**Managing connectors includes:**

* **Connectors Health:** Displays the current status of each connector, with a **green** icon for active connections and a **red** icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including databases, tables, columns, and views.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the **Nine Dots** menu.

* **Edit Connector:** Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Profiler**: Customize data profiling rules and methods.&#x20;
  * **Access Instructions:** Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector:** Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

## Limitations

<table><thead><tr><th width="110.25">S.No.</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td><p>Data Profiling for the following data type columns is not supported:</p><ul><li>My SQL: “Long blob”, “blob”</li><li>PostGreSQL : “bytea", "jsonb", "lseg", "polygon", "json", "box",</li></ul><p>"macaddr", "line", "point", "array", "xid", "anyarray", "oidvector", "int2vector", "bytea", "tid", "pg_lsn","user-defined", "uuid", "hstore", "int4range", "int8range", "numrange", "tsrange", "tstzrange", "daterange”</p></td></tr><tr><td>2.</td><td>Data Profiling limit for column length - supports up to 50,000.</td></tr></tbody></table>

## Connectivity Troubleshooting

<table><thead><tr><th width="84">S.No.</th><th width="189.5">Error Message(s)</th><th>Error Description / Resolution</th></tr></thead><tbody><tr><td>1</td><td>Failed to establish a connection. Please check the credentials.</td><td><p><strong>Error Description</strong></p><p>The primary reason for this error is usually incorrect or invalid credentials (username or password).</p><p><strong>Error Resolution</strong></p><p>Verify the username and password, check the connection string format, ensure network connectivity, review user access permissions, and validate the database endpoint.</p></td></tr><tr><td>2</td><td>Connection Timeout</td><td><p><strong>Error Description</strong></p><p>The "Connection Timeout" error occurs when the connector is unable to establish a connection to the Aurora database within a specified time period. This can be due to network issues, incorrect configuration settings, or server unavailability.</p><p><strong>Error Resolution</strong></p><p>Check network connectivity, verify the endpoint and port, review firewall and security group settings, increase timeout settings, ensure the database server is running, reduce network latency, and consult logs for details.</p></td></tr><tr><td>3</td><td>Warning for unsupported data types while profiling</td><td><p><strong>Error Description</strong></p><p>Warning for column SampleTable.column_binary but continuing operation. Skipping profile for unsupported data type binary.</p><p><strong>Error Resolution</strong></p><p>Convert unsupported data types to supported ones if profiling is important. For example, change binary data to VARBINARY or BLOB if supported. Check for updates or plugins for your profiling tool that add support for more data types.</p></td></tr></tbody></table>

## FAQs

<details>

<summary>How much does the driver cost?</summary>

The JDBC Driver for AWS Aurora is available at no additional charge.

</details>

<details>

<summary>Can I use the driver to access AWS Aurora from a Linux system?</summary>

Yes! You can use the driver to access AWS Aurora from Linux, Unix, and other non-Windows platforms.

</details>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/amazon-aurora.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.