...
- 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 is notified when Jira items moved to Submitted (how?)
The ACRG should then:
- 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
- All Basic Info fields submitted?
- All Justification questions addressed?
- All Cost Management Plan questions addressed?
- All answers reasonable?
- Determine whether the purchase of reserved instances is warranted based on the length of time the environment is expected to exist. Reserved instances can be purchased for dedicated RDS and OpenSearch instances.
- Once approved, notify Treasurer (how?) to be aware of potential impact.
- If denying the request, explain in writing and notify Community Council.
...