Skip to content

Migrate Postgres RDS from AWS to Philly Cluster #464

Closed

Description

@TineoC

Description

The goal of this task is to migrate the final AWS-hosted component—Postgres—to the Philly Cluster. This involves deploying a new pgcluster with pgvector features enabled and performing a data migration from the current AWS RDS instance.

Scope of Work

  • Infrastructure Setup: Deploy pgcluster in both cfp-sandbox and cfp-live environments.
  • Feature Enablement: Enable pgvector features on the new clusters.
  • Data Migration: Migrate existing data from AWS RDS to Philly Cluster.
  • Traffic Shifting: Implement a Blue-Green deployment to route a percentage of requests to the new pgcluster to avoid disruption.
  • Validation: Monitor performance and parity before 100% cutover.

Strategy: Blue-Green Deployment

To avoid disruption in the dev and live environments, we will shift a percentage of requests from the current app to RDS and another to the new pgcluster.

Related Pull Requests

  • PR # (To be linked): Infrastructure deployment for pgcluster
  • PR # (To be linked): Configuration changes for pgvector and traffic splitting
  • PR # (To be linked): Final cutover and RDS cleanup

Staheholders

Activity

  1. themightychris commented on Feb 18, 2026

    @themightychris
    Member

    we've been wanting to deploy CNPG to the clusters and start time that to host databases for projects, instead of the usual creating a statefulset within each project. Anyone game to try helping stand that up as part of this?

  2. TineoC commented on Feb 18, 2026

    @TineoC
    CollaboratorAuthor

    Yea I would first learn how to deploy PG vector on k8s first and then would see how this could be solved for the sandbox environment.

  3. themightychris commented on Feb 19, 2026

    @themightychris
    Member

    The process will be very different between using CNPG and not using CNPG

  4. sahilds1 commented on Feb 21, 2026

    @sahilds1
    Collaborator

    @TineoC Thanks for the helpful information in this ticket! Here are my questions right now

    • What would be the recommended local dev setup after this migration? Would we be able to connect to the sandbox?
    • Would we be able to read from the new pgcluster for analytical queries?
    • Shall we create a Slack channel for this migration so devs can watch for updates?

    cc @themightychris @taichan03

  5. themightychris commented on Feb 21, 2026

    @themightychris
    Member

    What would be the recommended local dev setup after this migration? Would we be able to connect to the sandbox?

    ideally in local dev you have a script that can initialize a local DB. Long term using a shared DB for local dev becomes challenging without heavy coordination.

    If a seed script or data generator isn't practical because the system relies on a bunch of real data being loaded, another good approach is to maintain a dumb of the sandbox DB in a cloud bucket and have a script local devs can run to bootstrap that downloads and loads that

  6. moved this to Backlog in Balanceron Feb 25, 2026
  7. moved this from Backlog to In Progress in Balanceron Feb 25, 2026
  8. moved this from In Progress to Priority in Balanceron Mar 11, 2026
  9. moved this from Priority to In Progress in Balanceron Mar 31, 2026
  10. TineoC commented on Jun 27, 2026

    @TineoC
    CollaboratorAuthor
  11. TineoC commented on Jun 27, 2026

    @TineoC
    CollaboratorAuthor

    the migration was in place now we're ready to follow up with the cut-over to pgcluster and after, remove the aws rds instance @taichan03

  12. moved this from In Progress to Done in Balanceron Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

  • Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions