...
- 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?
- Mark Veksler suggested: Maybe want to develop a calculator? Or an excel spreadsheet? Including all of the AWS components involved. Yogesh Kumar Peter Murray ? Make as simple as possible for development team.
- Impact / risks if the request is declined.
Cost Management Plan
- Will Has 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/7reviewed the Off-hour Environment Downscale policy? Will the dev team be requesting a shorter weekly shutdown period than indicated by the Shutdown Schedule?
- 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”
...