Environments
A description of the serverless environments.
Last updated
A description of the serverless environments.
Last updated
Three environments are cloud-hosted in AWS.
A group of senior engineers will get PowerUser permissions in this environment. This will allow them to create resources of all types and fuck them up pretty bad without causing damage outside of their localized team and project.
Limited access to manager and QC only. Integration testings, etc, will occur here before deploying to production. No one should ever really need to have or be granted access to this space. Its purpose is to be part of the CICD pipeline and do the heavy lifting of stress tests and integration tests, building, and deploying.
Highest security EC2 instance. Any senior developer with correct SSH keys can log in and deploy to Cerberus; only Cerberus can run final tests and deploy to production.
Access to these resources should be extremely limited and only be granted to trusted individuals with a deep knowledge of the application and familiar with security vulnerabilities, etc. Or, if it’s 2022, you give it to interns that don’t know what they are doing and to an owner that knows even less.
