Postgres connection logging

For security monitoring and compliance audits, Postgres can log connection lifecycle events to your project's Postgres logs, including events such as connection received, connection authenticated, and connection authorized.

Default behavior#

By default, Supabase sets log_connections to off for new projects and you must enable it first. This behavior matches common managed Postgres defaults and reduces log volume from high-frequency connection events.

Existing projects may retain different settings depending on plan and compliance configuration:

• Team, Enterprise, and HIPAA organizations — Connection logging is typically enabled to support audit requirements.
• HIPAA projects — Supabase enables connection logging when a project is marked as high compliance. The Security Advisor warns if connection logging is later disabled.

Compliance considerations#

Connection logging supports audit and monitoring controls required by some compliance programs:

• HIPAA — High-compliance projects should keep connection logging enabled. See the shared responsibility model for healthcare data and HIPAA compliance guide.
• SOC 2 — Users who need connection audit evidence should enable logging and retain logs according to their own policies. See the SOC 2 compliance guide.

Disabling connection logging does not affect other Supabase logging (for example, Platform Audit Logs, Auth Audit Logs, or pgAudit).

Manage connection logging via the dashboard#

You can configure connection logging from the Log connections setting in the Database Settings section of the Dashboard.

Ensure that you have Owner or Admin permissions for the project.

Manage connection logging via the Management API#

You can also manage connection logging using the Management API:

1
# Get your access token from https://supabase.com/dashboard/account/tokens
2
export SUPABASE_ACCESS_TOKEN="your-access-token"
3
export PROJECT_REF="your-project-ref"
4
5
# Get current Postgres config
6
curl -X GET "https://api.supabase.com/v1/projects/$PROJECT_REF/config/database/postgres" \
7
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN"
8
9
# Enable connection logging
10
curl -X PUT "https://api.supabase.com/v1/projects/$PROJECT_REF/config/database/postgres" \
11
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \
12
  -H "Content-Type: application/json" \
13
  -d '{
14
    "log_connections": true
15
  }'
16
17
# Disable connection logging
18
curl -X PUT "https://api.supabase.com/v1/projects/$PROJECT_REF/config/database/postgres" \
19
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \
20
  -H "Content-Type: application/json" \
21
  -d '{
22
    "log_connections": false
23
  }'

To verify the setting, use the SQL Editor:

1
show log_connections;