Phase 2 Migration of Existing Production JPL AWS Infra to MCP

[jordanpadams]

💡 Description

Phase 2 includes move of production web presence to MCP

⚔️ Sub-tasks

• Migrate dev and prod EC2 instances and associated data to MCP portal-tasks#89
• Create baseline IAM policies for AWS resources in MCP #95
• Migrate dev and prod EC2 instances and associated data to MCP portal-tasks#89
• Set up appropriate policies for Dev/Test/Prod environments #97
• Migrate data and users from JPL AWS to MCP #98
• Migrate metrics / analytics

[jordanpadams]

📆 05/2024 status: Pushed to later in build plan due to delays in NASA-PDS/registry#185. This is an internal cost cutting/consolidation measure so no impact on delivery to customers.

[jordanpadams]

📆 06/2024 status: Pushed again to later in build plan due to delays in NASA-PDS/registry#185. This is an internal cost cutting/consolidation measure so no impact on delivery to customers.

[jordanpadams]

📆 07/2024 status: Start delayed an additional couple sprints. This is an internal cost cutting/consolidation measure so no impact on delivery to customers.

[jordanpadams]

@viviant100 @sjoshi-jpl FYI, this is next very high priority task for us. if this is something the SAs can help with let's do it. Let me know if there is any testing or anything you need from me.

[jordanpadams]

📆 08/2024 status: Operations task deferring to B15.1. No impact on delivery to customers.

[jordanpadams]

@sjoshi-jpl FYI, per our schedule, this task is up. we can talk about this next week, but we should start with moving the node data backup accounts to MCP (ping @viviant100 for more info on this) and the web logs bucket. we are currently testing upgrades for the EC2s that should be complete in the next week or so and ready for a migration.

[jordanpadams]

📆 11/2024 status: Started. On Schedule.

[jordanpadams]

📆 12/2024 status: Start delayed 1 sprint. Kicked off week of 1/5/25. To be extended 2 sprints. Primarily SA task. No impact on dev work.