...
Required Information in a New Environment Request
Basic Info (one-liners)
- Dev Team. Who will be using the environment?
- Purpose. Specific feature(s) being tested?
...
- Modules. Primary module(s) related to the purpose of the environment.
- Expected Start Date
- Expected End Date
...
- Or perhaps, during what flower releases’ development will it be needed?
- Data Set / Size.
...
Justification
...
Justification
- Expand on the purpose as necessary. Why is this new environment needed?
- Are there any existing environments serving the same team and/or modules? If so, explain why they are not sufficient for this need.
- Cost estimates: a) monthly and b) total for the life of the environment.
- Are there any past (or still existing) environments that were used in a similar manner, such that this environment would likely have similar monthly costs?
- Impact / risks if the request is declined.
Cost Management Plan
- Will the dev team be following the “pausing/stopping” guidelines? Explain any planned divergence from those guidelines.
- Refers to “D4: Define guidelines/best practices around pausing/stopping environments when they're not in use - e.g. off-hours/weekends/etc.”
- Specifically what will be the expected operating hours? Or will it need to run 24/7?
- What budgets, budget alerts, cost anomaly detection will be used?
- Refers to “D5. Create AWS Budgets and AWS Budget Alerts for daily and monthly spend rates” and “D6. Explore AWS Cost Anomaly Detection and Rightsizing Recommendations”
Approval Process
- AWS Cost Review Group notified when Jira items moved to Submitted (how?)
- Within two weeks: either approve, deny, or ask questions on the Jira.
- PO and Dev Lead expected to respond to any questions, meet to discuss synchronously if requested.
- Approval Checklist
- Reasonable answers?
- Reasonable answers?
- All required fields submitted?
- All Justification questions addressed? Reasonable answers
- ?
- All Cost Management Plan questions addressed? Reasonable answers
- ?
- Once approved, notify Treasurer (how?) to be aware of potential impact.
...