Hints

  • Re-platforming into managed service (like Amazon Relational Database Service) is favored over re-hosting into AWS EC2
  • When migrating database, make sure the source system downtime is minimized (for example by using continous data replication)
  • When creating Amazon RDS instance disable Enhanced Monitoring (otherwise you will get privileges error) - while enabling Enahanced Monitoring is a very good idea in general, limitations of privileges of your role in this GameDay require disabling the functionality
  • Disable data validation in DMS Replication Task to save time (in real life validation is be a good idea though :))

Steps for replication of database with AWS Database Migration Service

  1. Create an Amazon RDS database
  2. Create DMS Replication Instance (more details)
    • Make sure it has access both to public internet (for source database) and the target database
    • Make sure it runs in a public subnet by creating a subnet group with public subnets only (more details)
  3. Create DMS Source and Target Endpoints (more details)
  4. Update Source Database (if needed, e.g. for Continous Data Replication)
  5. Create and run DMS Replication Task (more details)