Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS SSL certificates migration #13

Open
lpalbou opened this issue Mar 19, 2020 · 2 comments
Open

AWS SSL certificates migration #13

lpalbou opened this issue Mar 19, 2020 · 2 comments

Comments

@lpalbou
Copy link
Contributor

lpalbou commented Mar 19, 2020

The following announcement could impact both the GO-CAM website and the GO-CAM API as they are working with AWS SSL: https://aws.amazon.com/blogs/security/how-to-prepare-for-aws-move-to-its-own-certificate-authority/

At the moment, this doesn't seem to affect us, but will have to be monitored.

@kltm
Copy link
Member

kltm commented Mar 19, 2020

@lpalbou Thank you for adding this--I still hadn't fully process those announcements.

These sites still work without HTTPS, correct? As we circle around and start treating with geneontology/go-site#53 more seriously, we can coordinate a common way forward.

@lpalbou
Copy link
Contributor Author

lpalbou commented Mar 19, 2020

I just checked; yes the API works also in HTTP but the site currently has an autoredirect http -> https through cloudfront. Should an issue happened, this is an easy fix.

That would be nice indeed to have all services running HTTPS. I would start by low level services such as GOLr, blazegraph & barista. Once those are HTTPS, we can proceed with the UIs tools

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

No branches or pull requests

2 participants