Encrypt DevHub Backend

[kj4ezj]

Following devrel issue 134 and issue 135, this issue has me adding SSL or TLS encryption between the DevHub frontend and the DevHub backend. This entails issuing a certificate to the backend database server, which is currently an IP address. Depending on the certificate issuer, The backend will need a valid domain name issued to it in order to get a certificate. Cross-site scripting attacks have to be considered here, as even a valid domain name and certificate issued to the database backend may trigger browser protections against such an attack if the domain for the backend is too dissimilar.

See Also

• devrel issue 80 - Standup DevHub Infrastructure
• devrel issue 96 - DNS Mapping for learn.eosnetwork.com
• devrel issue 134 - Update DevHub Site
• devrel issue 135 - DevHub Frontend CICD
• devrel issue 137 - Encrypt DevHub Backend
• devhub issue 12 - Put AWS Resources into Terraform with a CICD Deployment
• devhub issue 13 - Document CICD System
• devhub issue 14 - Staging Environment
• devhub issue 15 - Backend CICD
• devhub issue 16 - Structures CICD
• devhub issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
• devhub issue 18 - Add BASH Linters for CICD Code
• devhub issue 19 - Include Test Suite in CICD

[kj4ezj]

This is done, check it out!

dig api.learn.eosnetwork.com
curl -f https://api.learn.eosnetwork.com/test