# AlloyDB — PostgreSQL

Integrate, catalog, and govern AlloyDB for PostgreSQL assets in Atlan.

## Required permissions

- [Preflight checks for AlloyDB for PostgreSQL](https://docs.atlan.com/llms/connectors/alloydb-postgresql/preflight-checks-for-alloydb-postgresql/llms.txt): Verify prerequisites before setting up the AlloyDB for PostgreSQL connector

## Setup options

- [Set up AlloyDB for PostgreSQL](https://docs.atlan.com/llms/connectors/alloydb-postgresql/set-up-alloydb-postgresql/llms.txt): Configure authentication and connection settings for AlloyDB for PostgreSQL connector
- [Choose how Atlan connects to AlloyDB for PostgreSQL](https://docs.atlan.com/llms/connectors/alloydb-postgresql/choose-how-atlan-connects-to-alloydb-postgresql/llms.txt): Compare the three ways Atlan can reach your AlloyDB for PostgreSQL instance - the self-deployed runtime, Private Service Connect, and public IP with authorized networks.
- [Allowlist Atlan IPs in AlloyDB authorized networks](https://docs.atlan.com/llms/connectors/alloydb-postgresql/allowlist-atlan-ips-in-alloydb-authorized-networks/llms.txt): Enable a public IP on your AlloyDB for PostgreSQL instance and admit only Atlan's tenant-specific egress IPs through authorized networks.
- [Connect through self-deployed runtime](https://docs.atlan.com/llms/connectors/alloydb-postgresql/connect-through-the-self-deployed-runtime/llms.txt): Connect Atlan to a private AlloyDB for PostgreSQL instance with the self-deployed runtime - a small service in your network that reads AlloyDB locally and sends metadata out over outbound-only HTTPS.
- [Set up Private Service Connect to AlloyDB](https://docs.atlan.com/llms/connectors/alloydb-postgresql/set-up-private-service-connect-to-alloydb/llms.txt): Let Atlan's SaaS reach your AlloyDB for PostgreSQL privately over Google's internal network - no public IP, nothing deployed on your side beyond a service attachment.
- [Special cases](https://docs.atlan.com/llms/connectors/alloydb-postgresql/special-cases/llms.txt): AlloyDB for PostgreSQL special cases - fleets of instances, very large databases, cross-cloud tenants, and connection paths that rewrite the port.

## Reference

- [How Atlan connects to AlloyDB Postgres](https://docs.atlan.com/llms/connectors/alloydb-postgresql/how-atlan-connect-to-alloydb-postgres/llms.txt): Understand how Atlan securely connects to your AlloyDB Postgres database to extract metadata.
- [How AlloyDB connectivity works](https://docs.atlan.com/llms/connectors/alloydb-postgresql/how-alloydb-connectivity-works/llms.txt): Learn why AlloyDB for PostgreSQL is hard to reach from outside, and what each of the three connection paths - self-deployed runtime, Private Service Connect, and public IP - actually does.
- [What does Atlan crawl from AlloyDB for PostgreSQL](https://docs.atlan.com/llms/connectors/alloydb-postgresql/what-does-atlan-crawl-from-alloydb-postgresql/llms.txt): Atlan crawls and maps the following assets and properties from AlloyDB for PostgreSQL

## Troubleshooting

- [Troubleshooting AlloyDB connectivity](https://docs.atlan.com/llms/connectors/alloydb-postgresql/troubleshooting-alloydb-connectivity/llms.txt): Symptom-first troubleshooting for AlloyDB for PostgreSQL connectivity - private IP errors, PSC handshake failures, IAM authentication issues, grants, large crawls, and sudden breakage.