Document EVM Cloud Network Infrastructure
Closed this issue · 1 comments
Following issue 404 and engineering issue 38, this ticket is to document the cloud infrastructure used to stand up the seven EOS-EVM public endpoints.
As much of this documentation should live in this repo as possible. However, thorough documentation that would be useful to engineers expected to maintain this infrastructure may include sensitive information such as IP addresses, DNS names, security configurations, account numbers, regions, etc. Such information could be exploited by attackers, so this part of the documentation will need to live in the internal documentation repo.
Ideally, the public documentation would be a complete picture for someone wishing to understand how the infrastructure works or how to stand up their own, while the private documentation would only include our implementation-specific details. Another way to think about it might be that the public docs are what we would define in terraform, and the private docs are what we would map in as secrets (but don't put passwords or keys in GitHub, obviously).
Accepted via PR #25