Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anomalyarmor.ai/llms.txt

Use this file to discover all available pages before exploring further.

In this step, you’ll add your first database connection to AnomalyArmor. This establishes the secure link that allows us to discover and monitor your data assets.

​
Before You Begin

Make sure you have:
  • Database hostname, port, and credentials
  • Network access from AnomalyArmor to your database (see Quickstart Overview)
  • A read-only database user (recommended)

​
Supported Databases

DatabaseVersionNotes
PostgreSQL12+Including RDS, Aurora, Supabase
DatabricksUnity CatalogRequires access token
ClickHouse21+Including ClickHouse Cloud

​
Step-by-Step Guide

1

Navigate to Asset Management

From the AnomalyArmor dashboard, click Settings in the left sidebar, then select the Assets tab.You’ll see the Asset Management page with a list of your existing connections (empty if this is your first time).
2

Click Add New Asset

Click the Add New Asset button. You can find this button in the top right corner of the page, or in the center of the page if you have no assets configured yet.
3

Select Database Type

Choose your database type from the available options:
  • PostgreSQL - For PostgreSQL, Amazon RDS, Aurora, Supabase, etc.
  • Databricks - For Databricks with Unity Catalog
  • ClickHouse - For ClickHouse or ClickHouse Cloud
4

Enter Connection Details

Fill in your connection information:
FieldDescriptionExample
Connection NameA friendly name for this connectionProduction PostgreSQL
HostDatabase hostname or IPdb.example.com
PortDatabase port5432
DatabaseDatabase nameproduction
UsernameDatabase useranomalyarmor_reader
PasswordUser password••••••••
SSL ModeSSL configurationrequire (recommended)
PostgreSQL connection form
5

Test Connection

Click Test Connection to verify AnomalyArmor can reach your database.
Successful connection test result
If the test fails, see the Troubleshooting section below.
6

Save Connection

Click Save to add the connection.You should see your new asset in the Asset Management list with a “Ready” status.

​
What Happens Next

After saving your connection:
  1. Credentials are encrypted: Stored securely with AES-256 encryption
  2. Connection is ready: You can now run discovery to scan your database
  3. No data accessed yet: Discovery must be triggered manually or scheduled

​
Security Best Practices

Always use a read-only, dedicated user for AnomalyArmor. Never use your application’s production credentials.

​
Creating a Read-Only User

-- Create a dedicated user
CREATE USER anomalyarmor WITH PASSWORD 'your-secure-password';

-- Grant minimal required permissions
GRANT CONNECT ON DATABASE your_database TO anomalyarmor;
GRANT USAGE ON SCHEMA public TO anomalyarmor;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO anomalyarmor;

-- For future tables (optional but recommended)
ALTER DEFAULT PRIVILEGES IN SCHEMA public
GRANT SELECT ON TABLES TO anomalyarmor;

​
Troubleshooting

Cause: Network connectivity issuesSolutions:
  1. Verify the hostname and port are correct
  2. Check that your database is running
  3. Ensure AnomalyArmor IPs are allowlisted in your firewall/security group
  4. For RDS: Verify the security group allows inbound traffic on your DB port
# Test connectivity from your machine
nc -zv your-host.rds.amazonaws.com 5432
Cause: Invalid credentialsSolutions:
  1. Double-check username and password (copy-paste to avoid typos)
  2. Verify the user exists in the database
  3. Ensure the user has CONNECT permission on the database
  4. Check for special characters in password that may need escaping
Cause: Database requires SSL but connection isn’t using itSolutions:
  1. Set SSL Mode to require in the connection form
  2. For RDS: SSL is required by default, ensure SSL Mode is set
  3. For self-hosted: Verify SSL certificates are properly configured
Cause: Network latency or firewall issuesSolutions:
  1. Verify the database is accessible from outside your VPC
  2. Check for firewall rules blocking the connection
  3. For private databases: Contact us about VPC peering options
Cause: User lacks required permissionsSolutions:
  1. Grant SELECT on information_schema tables
  2. Grant USAGE on the schema you want to monitor
  3. Verify user can access the specific database

​
Common Questions

​
What database permissions does AnomalyArmor need?

Read-only: CONNECT on the database, USAGE on the schemas you want monitored, and SELECT on tables. ALTER DEFAULT PRIVILEGES is optional but recommended so new tables are picked up automatically. No write, DDL, or admin permissions are ever needed.

​
Can I connect AnomalyArmor to a database inside a private VPC?

Yes, via three options: IP allowlisting from AnomalyArmor’s static outbound IPs (visible in Settings → Security), VPC peering, or AWS PrivateLink. The last two require an Enterprise plan and a short setup call. See Connection Issues for diagnosing network reachability.

​
Does AnomalyArmor support Amazon RDS, Aurora, and Supabase?

Yes. These are PostgreSQL-compatible and work with the PostgreSQL connector. RDS and Aurora require SSL; set SSL Mode to require on the connection form. Supabase requires the direct database connection string, not the pooler URL, for freshness queries to return accurate timestamps.

​
Why should I create a dedicated read-only user instead of reusing an existing one?

Blast radius. A dedicated user means you can audit exactly what AnomalyArmor runs, rotate credentials without breaking other systems, and apply minimal permissions. The Query Gateway already blocks writes and full-row reads, but a read-only user at the database layer is defense in depth.

​
My connection test fails with ‘Connection refused’ - what’s wrong?

Almost always a firewall or security-group issue. Verify your database accepts inbound traffic on its port from AnomalyArmor’s static IPs (listed in Settings → Security). For RDS, check the security group inbound rules. For self-hosted databases, confirm listen_addresses in PostgreSQL config allows external connections.

​
Next Step

Your database is connected! Now let’s discover your tables and schemas.

Run First Discovery

Scan your database to catalog tables, views, and columns