- Industry
- Insure AI
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Head of Platform Engineering
- Code
- ENG-11
It provisions and maintains the cloud infrastructure for the insurance platforms with infrastructure as code, keeping policy, claims and health data in approved regions, encrypted and tagged. It plans changes for production and applies non-production changes itself.
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 account: the current infrastructure state and costs..
- 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 Platform Engineering with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens the infrastructure change with its plan. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The infrastructure standards, approved regions and data residency rules, tagging policy, network rules and cost limits.
Reads from
the cloud account: the current infrastructure state and costs.
Acts in
the code repository: it opens the infrastructure change with its plan.
Hands back
An object with resources (a list), plan_summary, monthly_cost, data_classes, region and apply (now or on_approval).
Asks a person when
The change is in production, exposes anything publicly, holds health data, or costs over 2000 a month.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Monthly cost without approval (USD) | 2000 | Above this needs approval. |
| Required tags | owner, system, data_class, cost_centre | Comma-separated. |
| Approved regions | us-east, us-west | Where policy and claims data may live. |
| Apply non-production itself | On | When on, non-production changes apply directly. |
| May expose publicly | Off | When off, nothing is public without approval. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep policy, claims and health data only in us-east, us-west, encrypted at rest and in transit.
- Tag every resource with owner, system, data_class, cost_centre.
- When off is false, nothing is internet-facing without approval.
- Changes costing over 2000 a month need the Head of Platform Engineering.
- When on is true, apply non-production changes; production changes are planned for approval.
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.