Ignite: Migrating A Legacy App to Modern Infrastructure
summary
A 4 node Linode app becomes 6 node + RDS on AWS and the migration succeeds with few data problems; the database is small so the pg_restore inside AWS finishes quickly but RDS limitations force changes to restores and superuser-only operations. Deploy tooling is concrete: terraform for infra, ansible and retained Capistrano for deploys. Static assets move to S3 but private URLs break emails, Elasticsearch rebuilds are single-threaded across nodes, and initial security groups are misconfigured. Trello holds the checklist.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:41App Overview
- 0:56Initial provisioning
- 1:11New infrastructure
- 1:26Data migration
- 1:56Logical Components
- 2:11Ant Full
- 2:41API Keys
- 2:56SSH Keys
- 3:12Python
- 3:27RDS
- 4:11Trello
- 4:26Planning
- 4:42Tools Used
- 4:57Retrospective
related talks
01h 03mContinuous Security in the Cloud
35mMigrating Your Old Server Products to Be Stateless Cloud Services
05mIgnite - What I Learned From a Dress an On-Call Nightmare
50mHow to be cool in the age of legacy
21mAvoiding That $1M Dollar AWS Bill - Mark Michael, Glenn Oppegard
06mIgnite - Blue Green Deployments Using Terraform + Packer + Jenkins
35mMigrating a live site across the country without downtime
49mHardware to AWS, EC2 to EKS: Two Years, Two Epic Migrations