Deploy doi-ui in production on AWS - Githubissues

NASA-PDS / doi-ui

The web interface for the PDS DOI Service providing the ability management PDS archive DOIs. See the DOI Service for more details on the available capabilities. https://nasa-pds.github.io/doi-service/

Apache License 2.0

0 stars 4 forks source link

Deploy doi-ui in production on AWS #143

Closed tloubrieu-jpl closed 2 years ago

tloubrieu-jpl commented 2 years ago

💪 Motivation

...so that it can be used for real.

📖 Additional Details

The ui should use the doi-service in production as a back-end.
We should ask a different password than on pds-gamma to set the basic authentication on the doi-service and the doi-ui, so that a user can not by mistake create DOI in production.

⚖️ Acceptance Criteria

Given When I perform Then I expect

⚙️ Engineering Details

c-suh commented 2 years ago

@tloubrieu-jpl and @jordanpadams the documentation says to update the API endpoint to an absolute URL on gamma, but I'm assuming this should be relative so that they point to their respective databases. Please let me know if this isn't the case.

c-suh commented 2 years ago

The DOI-UI has been deployed, and the search has been tested for connection to the production database. The request for access authentication has been submitted with the SAs here, with information from the ticket for gamma and the distinction of a different password for production (2nd bullet point in Additional Details in the main description).

c-suh commented 2 years ago

Poked the SAs in the Slack channel.

jordanpadams commented 2 years ago

@c-suh sorry for the lack of clarity here. definitely set a relative path here. also, we do not want to distribute the ops password to anyone outside of EN until we have folks beta test the version on gamma

c-suh commented 2 years ago

jordanpadams no worries. I went ahead with the relative path and updated the documentation as well. Heard about the ops password (which is still TBD) - keep it internal until I get the green light from you or Thomas or Vivian.

Side note: deployed versions are

v2.2.0 for Service
v1.0.0 for UI

c-suh commented 2 years ago

SA provided a new password but it does not work. Have responded on the SA ticket.

c-suh commented 2 years ago

It's working! A few last details are being worked out regarding accessibility outside the firewall.

tloubrieu-jpl commented 2 years ago

I will close this ticket and open a new one to complete what remains to be done for the publication outside JPL VPN:

replace authentication with Cognito on ui and service
create an ASR for the application
do a security scan