Migrate pdscloud-* instances and pds.nasa.gov on MCP

[tloubrieu-jpl]

💡 Description

DRAFT TICKET TO BE COMPLETED...

We should do the following in 3 MCP environments (dev, stage, production)

Create the EC2 instances, using an MCP base image:

(only one EC2 instance on dev and stage, but 3 in prod, To Be confirmed) See wiki for details on EC2 names

Deploy all the services needed:

• [ ] legacy registry (solr)
• [ ] legacy harvest
• [ ] havest
• [ ] web site (apache and data)
• [ ] EFS mounted volumes for data (https://pds.nasa.gov/data/)
• [ ] DOI service TO BE COMPLETED

Configure the AWS services:

• [ ] cloudfront TO BE COMPLETED

Configure the DNS to go to the new EC2 instances on MCP:

• non production services private access from JPL (TO BE DEFINED e.g. http://pds.jpl.nasa.gov/dev/ http://pds.jpl.nasa.gov/stage/ )
• from NASA https://pds.nasa.gov/ , note https://pds.nasa.gov/api/* will need to implement a redirection to JPL AWS
• the API end-point need to be served from JPL AWS with a new URL, TO BE DEFINED

Alternative, we migrate the registry API to MCP but keep the back-end OpenSearch on JPL AWS. That would require some testing for the performances but if performances are ok, that would simplify the DNS configuration and the redirection management.

⚔️ Parent Epic / Related Tickets

No response