Engineering/Engineering Principles/4 Observability/Hosting Costs/

Hosting Costs

All hosting environments that incur a cost must have the expected cost documented · HC-01 · MUST · DEV

Each project must maintain a “Hosting Costs” page in the project wiki. This page must either:

  • Detail the expected monthly cost per environment, with the date of last review.
  • Link directly to the cloud provider’s cost management view for each environment (e.g. Azure Cost Management, AWS Budgets).

All environments must have a budget configured to alert on cost overruns · HC-02 · MUST · DEV

Configure a budget for each environment with alerts in the cloud provider’s cost management service. Alerts must notify the project team via agreed channels on cost overruns. Budget amounts must be kept up to date as resources are added, scaled or deprovisioned.

Tags must be used on the resource group to designate the environment and the customer · HC-03 · MUST · DEV

Apply tags on the resource group to enable accurate cost allocation. At a minimum, include:

  • environment: e.g. QA, UAT and Prod
  • customer: the client name or identifier

All budgets must be approved prior to creation or change · HC-04 · MUST · DEV

Budgets for any environment must be approved by IT before they are created, increased, or changed.

NOTE Approval of hosting costs for specific environments (e.g. Dev/QA) does not imply approval for other environments (e.g. UAT/Production), which may require separate formal sign-off.