Switch api.ooni.io to be served from AWS
Open
Nobody has claimed this yet.
epic
- Dominant language
- HCL
- Stars
- 4
- Forks
- 15
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 4
Description
This is about starting to use the AWS frontend as the real frontend for probes/explorer/etc.
Once we feel confident that all the services which we have rewritten are working as intended with the rest and that the setup on AWS is not going to lead to any downtime, we should make the switch.
We should do in two stages:
- Have a main entry point which is
api.ooni.organd configure Explorer and Probes to speak to it and validate that everything is working as intended - Change DNS to have
api.ooni.iopoint to AWS and have the load balancer rules just transparently proxy everything - Make sure there is no more traffic hitting backend-fsn, if so port missing services over (see: https://github.com/ooni/backend/issues/807)
- Incrementally change the rules to enable one service at a time
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.