- Industry
- IT Company
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Head of Service Delivery
- Code
- ENG-11
It writes and reviews infrastructure-as-code changes that provision, resize and maintain cloud resources for managed-services clients and the SaaS platform, planning each change against current state, the client's landing-zone rules and the data-residency terms in their contract. It applies changes to non-production itself and puts production changes through the change advisory process.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the cloud monitoring and observability stack: the current state, cost and tags of the client's or platform's resources..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Service Delivery with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it raises the change request with the plan and applies approved non-production changes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The cloud infrastructure standards: landing-zone rules per client, tagging, network and exposure rules, data-residency regions, ISO 27001 and SOC 2 controls, and the change management process.
Reads from
the cloud monitoring and observability stack: the current state, cost and tags of the client's or platform's resources.
Acts in
the ticketing and service management system: it raises the change request with the plan and applies approved non-production changes.
Hands back
An object with changes (a list with resource, action, region and monthly_cost_delta_usd), tag_check (pass or a list), residency_check (pass or a list), exposure (a list or empty), rollback and change_ticket (or null).
Asks a person when
The change is in production, costs more than 1500 USD a month, destroys a resource, exposes one publicly, or leaves the allowed regions.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Monthly cost change needing approval (USD) | 1500 | A change adding more than this a month needs the approver. |
| Required tags | client, environment, owner, cost_centre, data_classification | Comma-separated tags every resource carries. |
| Destroy allowed in | non_production_only | Where it may destroy resources. |
| Apply to non-production itself | On | When on, non-production changes apply without a person. |
| May expose resources publicly | Off | When off, no resource is reachable from the internet without approval. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Every resource carries client, environment, owner, cost_centre, data_classification; untagged resources are not applied.
- Place resources only in regions the client's contract allows; anything else is blocked.
- A change adding more than 1500 USD a month needs the Head of Service Delivery, and is billed to the client only as their managed-services contract allows.
- Destroy only as non_production_only allows and never without a backup check.
- Apply non-production changes when on is true; production goes through the change advisory process with a rollback.
- No public exposure unless off is true.
See the Infrastructure Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.