Skip to main content

How Atlan connects to AlloyDB Postgres

Atlan connects to your AlloyDB Postgres database to extract technical metadata while maintaining network security and compliance. You can choose between Direct connectivity for databases available from the internet or Self-deployed runtime for databases that must remain behind your firewall.

Connect via direct network connection​

Atlan's AlloyDB Postgres workflow establishes a direct network connection to your database from the Atlan SaaS tenant. This approach works when your AlloyDB Postgres database can accept connections from the internet.

Direct extraction

  • Atlan's AlloyDB Postgres workflow connects directly to your database from the Atlan SaaS tenant over port 5432 (default).
  • You provide connection details when creating a crawler workflow.
  • Atlan executes read-only SQL queries to discover your database structure and catalogs the results in Atlan Cloud.
  • Your AlloyDB Postgres database accepts inbound network connections from Atlan's IP addresses, controlled through your firewall rules or network security groups.

Connect via self-deployed runtime​

A runtime service deployed within your network acts as a secure bridge between Atlan Cloud and your AlloyDB Postgres database. This approach works when your AlloyDB Postgres database must remain fully isolated behind your firewall.

Self-deployed runtime extraction

  • A runtime service sits within your network perimeter, deployed on Docker Compose or a Kubernetes cluster.
  • The runtime maintains an outbound HTTPS connection to Atlan Cloud (port 443) and a local network connection to your AlloyDB Postgres database (port 5432).
  • When you create a crawler workflow, Atlan Cloud sends metadata extraction requests to the runtime through the outbound connection.
  • The runtime translates requests into SQL queries, executes them on your AlloyDB Postgres database, and returns the results to Atlan Cloud.
  • Your AlloyDB Postgres database never exposes ports to the internet—all connections are initiated from within your network.

How it protects your data​

AlloyDB Postgres databases contain critical business data and operational information. Atlan's connection architecture protects your environment through multiple security layers.

  • Metadata extraction, not data replication: Atlan extracts only structural metadata—schemas, tables, columns, and their relationships. The actual business data in your tables remains in your AlloyDB Postgres database. For example, if you have a CUSTOMERS table with customer records, Atlan discovers the table structure and column definitions, but never queries or stores the customer records themselves.

  • Read-only operations: All database queries are read-only SELECT statements. The connector can't modify data, create or drop database objects, or change any configuration. The AlloyDB Postgres user permissions you grant control exactly what the connector can access.

  • Credential encryption: AlloyDB Postgres connection credentials are encrypted at rest and in transit. In Direct connectivity, Atlan encrypts credentials before storage. In Self-deployed runtime, credentials never leave your network perimeter—the runtime retrieves them from your enterprise-managed secret vaults (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, or HashiCorp Vault) only when needed, and Atlan Cloud never receives or stores them.

  • Network isolation with Self-deployed runtime: Your AlloyDB Postgres database gains complete network isolation from the internet. The database only accepts connections from the runtime within your local network. The runtime itself only makes outbound HTTPS connections to Atlan Cloud, which your network team can control through firewall rules.

  • Libraries: AlloyDB Postgres under hood uses AlloyDB Python Connector to connect to alloydb and fetch metadata.

See also​