It’s easy to connect your database to Bigeye and start monitoring your data quality. Bigeye offers two setup options to connect your data source: direct connection or via an in network agent.
For simple and easy setup, we recommend 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 itself is also encrypted at rest (AWS RDS).
Find your data source below and follow the database specific instructions to get started. Note that there are some specific permissions required to support Bigeye features like lineage and metadata metrics.
- AWS Athena
- Databricks Deltalake
- MySQL (5.7+)
- Oracle (11g+)
- Postgres (10+)
- Redshift (Any)
- Microsoft SQL Server (2008+)
- Azure Synapse
Alternatively, you can provision an agent in your network to allow Bigeye to connect to your data sources. This adds additional layers of security for your data source over a traditional direct connection:
- Data source credentials remain within your data center
- Data source does not have to be opened to accepting connections from outside of your data center
- No ingress ports are required on your data center firewall
- mTLS is used to secure transport of data between the Agent and Bigeye. This is more secure than standard TLS.
- In addition to the encrypted transport (mTLS), the data itself is encrypted with a second set of keys before being transmitted.
Follow the installation guide to provision the Bigeye agent. Agent connection is supported for the following source types:
- AWS Redshift
- SQL Server
- SAP HANA
Updated 5 months ago