Flyio Core Workflow B

Fly.io Core Workflow B: Postgres, Volumes & Networking

Overview

Set up Fly Postgres, persistent Fly Volumes, and private networking between apps. Fly Postgres runs as a regular Fly app with automated replication. Volumes provide persistent NVMe storage attached to specific machines.

Prerequisites

• A data owner, documented locality/retention/backup/recovery requirements, and a staging environment with synthetic data.
• Scoped database and deployment identities, private-network policy, and a tested restore/rollback procedure.

Output

Maintain a storage/network receipt with resource references, region, encryption/access controls, backup/restore verification, owner, and recovery result. Do not include connection strings, records, or keys.

Examples

Create a disposable staging database and volume with fictional data, confirm an unauthorized app cannot reach it, and test a backup/restore without copying credentials to logs. Tear down only the validated disposable resources through the approved process.

Instructions

Step 1: Create Fly Postgres

# Create a Postgres cluster
fly postgres create --name my-db --region iad --vm-size shared-cpu-1x --volume-size 10

# Attach to your app (sets DATABASE_URL secret automatically)
fly postgres attach my-db -a my-app

# Connect directly
fly postgres connect -a my-db
# psql> SELECT version();

# Proxy to local machine for dev tools
fly proxy 5432 -a my-db
# Now connect with the secret-bearing URL supplied by the local proxy
psql "$DATABASE_URL"

Step 2: Create Persistent Volumes

# Create a volume (same region as your machine)
fly volumes create data --size 10 --region iad -a my-app

# List volumes
fly volumes list -a my-app

# Mount in fly.toml

# fly.toml
[mounts]
  source = "data"
  destination = "/data"

# Deploy to pick up mount
fly deploy

# Verify mount inside machine
fly ssh console -C "df -h /data"

Step 3: Private Networking (6PN)

# Apps in the same org can reach each other via .internal DNS
# my-app can reach my-db at: my-db.internal:5432

# Internal DNS format: <app-name>.internal
# Machine-specific: <machine-id>.vm.<app-name>.internal

# Example: connect from app code
DATABASE_URL=${FLY_DATABASE_URL}

// Access internal services (no public internet)
const dbUrl = process.env.DATABASE_URL;
const apiUrl = `http://my-api.internal:3000/health`;  // Internal HTTP

Step 4: Postgres Backups and Failover

# List backups
fly postgres barman list-backups -a my-db

# Create manual backup
fly postgres barman backup -a my-db

# Check replication status
fly postgres barman check -a my-db

# Failover to standby (if primary fails)
fly postgres failover -a my-db

Error Handling

Resources

• Fly Postgres
• Fly Volumes
• Private Networking

Next Steps

For common errors, see flyio-common-errors.