Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Initial deployment of API on AWS - Fargate solution #165

Closed
jimmie opened this issue May 13, 2021 · 5 comments
Closed

Initial deployment of API on AWS - Fargate solution #165

jimmie opened this issue May 13, 2021 · 5 comments
Assignees
Labels

Comments

@jimmie
Copy link
Member

jimmie commented May 13, 2021

Provide POC-level deployment of registry api service within AWS Fargate. Originally thought this had been addressed as part of #122, but have since been proven incorrect in terms of issues with the ELB. Hopefully these can be addressed as soon as permission and certificate issues can be straightened out.

@tloubrieu-jpl
Copy link
Member

This still does not work so Jimmie and Suzan will start from something basic to identify the issue.

@jimmie
Copy link
Member Author

jimmie commented Jun 21, 2021

As of 6/21, the FG deployment is healthy and working. The last piece of the puzzle was to allow either 200 or 302 responses to be considered as healthy for an http request to the root URI.

@jimmie
Copy link
Member Author

jimmie commented Jun 21, 2021

Will consider completed.

@jimmie jimmie closed this as completed Jun 21, 2021
@tloubrieu-jpl
Copy link
Member

@jimmie will add the url

@tloubrieu-jpl tloubrieu-jpl reopened this Jun 22, 2021
@jimmie
Copy link
Member Author

jimmie commented Jun 24, 2021

registry api service endpoint is https://pds-en-ecs-894407400.us-west-2.elb.amazonaws.com - for now you will have to acknowledge acceptance of self-created ssl certs (e.g. curl -k)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants