# Cloud SQL — PostgreSQL

Integrate, catalog, and govern Cloud SQL for PostgreSQL assets in Atlan.

## Required permissions

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

## Setup options

- [Set up Cloud SQL for PostgreSQL](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/set-up-cloud-sql-postgresql/llms.txt): Configure authentication and connection settings for Cloud SQL for PostgreSQL connector
- [Choose how Atlan connects to Cloud SQL for PostgreSQL](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/choose-how-atlan-connects-to-cloud-sql-postgresql/llms.txt): Compare the three ways Atlan can reach your Cloud SQL for PostgreSQL instance - public IP with authorized networks, the self-deployed runtime, and Private Service Connect.
- [Connect over public IP with authorized networks](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/connect-over-public-ip-with-authorized-networks/llms.txt): Connect Atlan to Cloud SQL for PostgreSQL over the instance's public IP, with Cloud SQL's authorized-networks list and SSL keeping everyone else out.
- [Connect a private-IP instance via self-deployed runtime](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/connect-a-private-ip-instance-via-the-self-deployed-runtime/llms.txt): Keep your Cloud SQL for PostgreSQL instance private - run a small Atlan-provided agent inside your network that reads metadata locally and sends it to Atlan over outbound HTTPS only.
- [Private Service Connect to Cloud SQL](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/private-service-connect-to-cloud-sql/llms.txt): Keep traffic between your GCP-hosted Atlan tenant and your Cloud SQL for PostgreSQL instance entirely on Google's internal network with Private Service Connect.
- [Special cases](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/special-cases/llms.txt): Cloud SQL for PostgreSQL special cases - IAM authentication done right, cross-cloud tenants, multiple instances and read replicas, and private IPs that quietly change.

## Reference

- [How Atlan connects to Cloud SQL Postgres](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/how-atlan-connect-to-cloud-sql-postgres/llms.txt): Understand how Atlan securely connects to your Cloud SQL Postgres database to extract metadata.
- [How Cloud SQL connectivity works](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/how-cloud-sql-connectivity-works/llms.txt): Learn the three traffic paths between Atlan and your Cloud SQL for PostgreSQL instance, who owns each piece, and why connectivity is not authentication.
- [What does Atlan crawl from Cloud SQL for PostgreSQL](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/what-does-atlan-crawl-from-cloud-sql-postgresql/llms.txt): Atlan crawls and maps the following assets and properties from Cloud SQL for PostgreSQL

## Troubleshooting

- [Future tables and permissions](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/future-tables-permissions/llms.txt): How to configure permissions for future tables created by any user in Cloud SQL for PostgreSQL
- [Troubleshooting Cloud SQL for PostgreSQL connectivity](https://docs.atlan.com/llms/connectors/cloud-sql-postgresql/troubleshooting-cloud-sql-postgresql-connectivity/llms.txt): Symptom-first troubleshooting for Cloud SQL for PostgreSQL connectivity - private IP errors, timeouts dressed as auth failures, SSL mismatches, IAM login, agent hangs, and PSC pending states.