Second Dashboard and AWS Migration

I already have a working login page that takes users straight into our original dashboard (Project A). The UI for a brand-new dashboard (Project B) is finished; what’s missing is the code that lets users choose which space to enter and the back-end move to our fresh AWS environment.

After a successful sign-in, users should see a clean dropdown menu listing the two project names. Their choice will load the corresponding dashboard without a second login or page refresh.

All data that currently feeds Project A sits on an old AWS server and is stored in S3. I want every table, file and setting moved to the new AWS server that will host Project B. I’d like this handled through AWS Database Migration Service, so familiarity with setting up DMS tasks, replication endpoints and the required IAM roles is essential.

New domain routing is already purchased for Project B; once migration is done, the domain must resolve to the correct dashboard while the original domain continues to serve Project A.

Deliverables
• Updated authentication flow with dropdown selector in place
• Both dashboards loading correctly from the single login page
• Complete data migration via AWS DMS, verified for accuracy and integrity
• DNS and SSL configured so each domain points to its respective dashboard
• Deployment notes or a short hand-over document for future maintenance

I’ll provide design files, AWS credentials (staging first, then production) and quick access to our current codebase. If you’ve integrated multi-dashboard portals and run S3-centric migrations before, this should be a smooth engagement.