Data Sources Overview

Connect AnomalyArmor to your databases and data platforms

Connect once, monitor everything. Add your database credentials and AnomalyArmor continuously monitors for schema changes, stale data, and quality issues, without installing anything in your infrastructure.

Your data stays in your database. We only read metadata (table names, column types, timestamps) through a secure, read-only connection.

Supported Databases

AnomalyArmor supports the most popular data platforms used by modern data teams:

Database	Version	Key Features
PostgreSQL	12+	Tables, views, schemas, materialized views
MySQL	5.7+	Tables, views, schemas
SQL Server	2012+	Tables, views, schemas, Azure SQL Database
Amazon Redshift	Any	Tables, views, external tables (Spectrum)
Databricks	Unity Catalog	Catalogs, schemas, Delta tables, views
ClickHouse	21.8+	Tables, views, materialized views, dictionaries

PostgreSQL

Including RDS, Aurora, Supabase, and self-hosted

MySQL

Including RDS, Aurora MySQL, PlanetScale, and self-hosted

SQL Server

Including Azure SQL Database and on-premise

Amazon Redshift

Provisioned clusters and Serverless workgroups

Databricks

Unity Catalog with Delta Lake support

ClickHouse

Including ClickHouse Cloud

How Data Sources Work

When you add a data source, AnomalyArmor:

1. Stores credentials securely: Encrypted with AES-256
2. Tests connectivity: Verifies we can reach your database
3. Awaits discovery: No scanning until you trigger it

What We Access

AnomalyArmor only queries metadata from your databases:

We Access	We Never Access
information_schema	Your actual data
System catalogs	Row contents
Table/column names	PII or sensitive values
Data types	Business data
Timestamps (for freshness)	Query results

See Security Overview for detailed information about our security practices.

Adding a Data Source

Quick Steps

1. Navigate to Data Sources in the sidebar
2. Click Add Connection
3. Select your database type
4. Enter connection credentials
5. Click Test Connection
6. Click Save

For detailed instructions, see the guide for your specific database:

• PostgreSQL Setup
• MySQL Setup
• SQL Server Setup
• Amazon Redshift Setup
• Databricks Setup
• ClickHouse Setup

Managing Data Sources

Editing Connections

To update a data source:

1. Go to Data Sources
2. Click on the connection name
3. Click Settings
4. Update credentials or configuration
5. Click Save

Changing credentials will require re-testing the connection. Scheduled discoveries may fail if credentials are incorrect.

Deleting Connections

To remove a data source:

1. Go to Data Sources
2. Click on the connection name
3. Click Settings → Delete Connection
4. Confirm deletion

What gets deleted:

• The connection and credentials
• Discovery schedule
• Associated alert rules (optional)

What’s preserved:

• Historical schema change data
• Audit logs

Connection Status

Each data source shows its status:

Status	Meaning
Connected	Last discovery succeeded
Error	Connection or permission issue
Never Run	Discovery hasn’t been triggered yet
Running	Discovery in progress

Network Requirements

AnomalyArmor connects outbound to your databases. You’ll need to:

1. Allow AnomalyArmor IPs

Allowlist our static IP addresses in your firewall or security group:

AnomalyArmor IP Addresses:
34.xxx.xxx.xxx/32
34.xxx.xxx.xxx/32

View current IPs in Settings → Security in your dashboard.

2. Open Database Port

Ensure the database port is accessible:

Database	Default Port
PostgreSQL	5432
MySQL	3306
SQL Server	1433
Amazon Redshift	5439
Databricks	443 (HTTPS)
ClickHouse	8443 (HTTPS)

3. SSL/TLS Configuration

We recommend (and often require) encrypted connections:

• PostgreSQL: SSL Mode = require
• MySQL: SSL Mode = require
• SQL Server: Encryption enabled (required for Azure SQL)
• Amazon Redshift: SSL required by default
• Databricks: Always HTTPS
• ClickHouse: Port 8443 for HTTPS

Enterprise Options

For enhanced security, Enterprise customers can use:

VPC Peering

Direct network peering between your AWS VPC and AnomalyArmor:

• No public internet exposure
• Lower latency
• Private IP connectivity

AWS PrivateLink

Connect via AWS PrivateLink:

• Fully private connectivity
• No firewall changes needed
• Traffic stays on AWS backbone

Contact [e-mail] for Enterprise options.

Best Practices

Use Read-Only Credentials

Always create a dedicated, read-only user for AnomalyArmor:

-- Example for PostgreSQL
CREATE USER anomalyarmor WITH PASSWORD 'secure-password';
GRANT CONNECT ON DATABASE your_db TO anomalyarmor;
GRANT USAGE ON SCHEMA public TO anomalyarmor;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO anomalyarmor;

Use Descriptive Names

Name your data sources clearly:

Good names:

• Production PostgreSQL
• Analytics Databricks
• Staging ClickHouse

Avoid:

• db1
• test
• connection

Start with One Environment

Begin with your production database, then expand to staging and development environments once you’re comfortable with the setup.

Troubleshooting

Connection test fails

1. Verify hostname and port are correct
2. Check credentials are valid
3. Ensure AnomalyArmor IPs are allowlisted
4. Verify SSL/TLS settings match your database

Discovery finds no tables

1. Verify user has SELECT on information_schema
2. Check schema filters aren’t excluding everything
3. Confirm tables exist in the monitored schemas

Intermittent connection errors

1. Check database availability and load
2. Verify network stability
3. Consider using a read replica for monitoring

Next Steps

Connect PostgreSQL

Full guide with RDS, Aurora, and Supabase instructions

Run Discovery

Scan your database after connecting