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

Come up with proper hostnames/references for prod SSH Observatory components #128

Open
claudijd opened this issue Jan 16, 2018 · 3 comments
Assignees

Comments

@claudijd
Copy link
Contributor

claudijd commented Jan 16, 2018

User Endpoint (this is the pre-existing endpoint users will go to to drive http/tls/ssh scans, it's not new, just referencing it):

  • observatory.mozilla.org

API Endpoint(s): (there are two of these simply so we can do staged roll outs without user impact, which we will likely hide behind an elb)

  • ssh-observatory-api1
  • ssh-observatory-api2

Database Endpoints: (this will be an RDS instance with high-availability/failover options, which is why there are not multiple)

  • ssh-observatory-db

Worker Endpoints: (there are two of these simply so we can do staged roll outs without user impact. Each worker server will be hosting multiple worker processes)

  • ssh-observatory-worker1
  • ssh-observatory-worker2
@claudijd claudijd self-assigned this Jan 16, 2018
@claudijd claudijd added this to In Progress in Move ssh_scan_api to AWS Jan 16, 2018
@claudijd
Copy link
Contributor Author

/cc @april thoughts/feedback?

@april
Copy link
Contributor

april commented Jan 17, 2018

I believe mine is called:

API endpoints:

  • http-observatory.security.mozilla.org (which are observatory-web1, observatory-web2)

And my Worker Endpoints are:

  • observatory-scanner1
  • observatory-scanner2

I think your names are better than mine though, so a solid r+ to you.

@claudijd
Copy link
Contributor Author

claudijd commented Jan 17, 2018

@april thanks for the feedback! I was missing the external endpoint for the ELB, I'll make sure to make that happen.

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

No branches or pull requests

2 participants