Connecting your database to Bigeye and monitoring your data quality is easy. Bigeye offers two setup options to connect your data source:

• Direct connection
• Agent connection

Direct connection

For a simple and easy setup, Bigeye recommends a direct connection. In general, direct connection requires you to allow-list Bigeye’s IP address, create a read-only service account in the data source, and add those credentials to Bigeye. Service account credentials are stored encrypted (AES-256), and the database file system is encrypted at rest (AWS RDS).

Find your data source below and follow the database-specific instructions to get started. Some specific permissions are required to support Bigeye features like lineage and metadata metrics.

• AWS Athena
• Redshift (Any)
• Azure Synapse
• BigQuery
• Databricks Deltalake
• Microsoft SQL Server (2008+)
• MySQL (5.7+)
• Oracle (11g+)
• Postgres (10+)
• SAP HANA
• Snowflake
• Trino
• Vertica

In Network Data Source Agent

Alternatively, you can provision an agent in your network to allow Bigeye to connect to your data sources. This method adds additional layers of security for your data source over a traditional direct connection:

• Datasource credentials remain within your data center.
• There is no requirement to open the data source to accept connections from outside of your data center.
• No ingress ports are required on your data center firewall.
• mTLS secures data transport between the Agent and Bigeye. It is more secure than standard TLS.
• In addition to the encrypted transport (mTLS), the agent network encrypts data with a second set of keys before transmission.

Follow the installation guide to provision the Bigeye agent. Agent connection is supported for the following source types:

• Athena
• AWS Redshift
• Databricks
• MySQL
• Oracle
• Postgres
• SAP HANA
• Snowflake
• SQL Server Keberos Authentication (agent only)
• Synapse
• Teradata
• Vertica