page:migrate:amazon rds for postgresql:relational records

Migrate Amazon RDS for PostgreSQL: Relational records

Move PostgreSQL data from Amazon RDS for PostgreSQL to Ample, one component at a time. Destination verified on Ample: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Source procedure: Take a logical backup with pg_dump -Fc from a network location that can reach the instance. Not migrated automatically: Multi-AZ failover, read replicas, IAM authentication, PITR and Performance Insights have no equivalent on the managed database. Cutover: Freeze writes at the source with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep RDS until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Representative Queries

Migrate Amazon RDS for PostgreSQL: Relational records
Where can I host Relational records?
I need a component-scoped export/import or reconfiguration procedure for Relational records, with compatibility checks, verification and rollback.

Resource Requirements

primitive:postgres

Infrastructure Requirements

Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Workload

Relational records

Migration Source

Amazon RDS for PostgreSQL

Execution Details

Release Status: published
Support Status: verified
Execution Status: unbound
Docs Only: true

Prerequisites

Authorized access to the Amazon RDS for PostgreSQL source and its export tooling
An inventory of every component in scope and out of scope
A validated backup or copy before any cutover
An Ample account token with servers:write, databases:read

Workflow Steps

Inventory the source: List what Amazon RDS for PostgreSQL provides beyond the component you are moving. Out of scope here: Multi-AZ failover, read replicas, IAM authentication, PITR and Performance Insights have no equivalent on the managed database.
Source step 1: Take a logical backup with pg_dump -Fc from a network location that can reach the instance.
Source step 2: Check the engine major version, extensions and parameter-group settings the app depends on.
Source step 3: Restore into a scratch managed database first and compare row counts.
Provision and restore: Deploy the app once to create a managed PostgreSQL 16 database (or run ample database create --engine postgres), then restore the dump with pg_restore using its connection string; keep migrations idempotent.
Validate before cutover: Run the app's own checks and compare counts and checksums.
Cut over: Freeze writes at the source, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep RDS until confirmed.
Rollback: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

Limitations

Documentation only: nothing is executed automatically and no execution binding is offered.
The source-side procedure is documented from Amazon RDS for PostgreSQL's standard tooling and was not executed in this catalog's evidence.
No full source-product parity is claimed: Multi-AZ failover, read replicas, IAM authentication, PITR and Performance Insights have no equivalent on the managed database.
Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.

Cost Estimate

Currency: USD
Monthly Amount: 10.0
Components:
- App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
- Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Evidence Summary

Destination side verified: the Express pattern fixture deployed on Ample and its checks passed.