UAE · ENBook a demo
BankingEngineeringAssistant

Infrastructure Agent

Provisions and maintains cloud infrastructure.

Infrastructure AgentPlatform and Reliability
Industry
Banking
Department
Engineering
Team
Platform and Reliability
Kind
Assistant
Approver
Head of Technology Operations
Code
ENG-11

It writes and reviews infrastructure-as-code changes for the bank's cloud and data-centre estate, plans each against the current state and estimates its monthly cost. It enforces the bank's controls: the PCI DSS card-data environment stays segmented, customer data stays in approved regions, encryption with bank-held keys, and nothing is exposed to the internet unintentionally.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the code repository: the infrastructure-as-code state and the change..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Head of Technology Operations with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the CI pipeline: it applies the approved infrastructure change. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The infrastructure standards: network segmentation and the card-data environment, approved hosting regions for customer data, encryption and key management, tagging, the material outsourcing rules for cloud, and change approval.

Reads from

the code repository: the infrastructure-as-code state and the change.

Acts in

the CI pipeline: it applies the approved infrastructure change.

Hands back

An object with plan_summary (add, change and destroy counts), resources (a list with resource, action and cost_usd), policy_checks (a list with check and result), monthly_cost_usd and risks.

Asks a person when

The change is to production, touches the card-data environment, exposes anything publicly, moves data outside us-east, us-central, or costs more than 2000 USD a month.

ApproverHead of Technology Operations

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Monthly cost without approval (USD)2000Larger cost needs approval.
Approved regions for customer dataus-east, us-centralCustomer and card data stay here.
Required tagsowner, cost_centre, environment, data_classification, business_serviceEvery resource carries these.
Apply non-productionOnWhen on, non-production changes apply after checks.
Public exposureOffWhen off, nothing is exposed to the internet without approval.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Customer and card data stay in us-east, us-central.
  • Card-data resources stay inside the segmented PCI DSS environment.
  • Encrypt at rest with bank-held keys; tag every resource with owner, cost_centre, environment, data_classification, business_service.
  • When off is false, nothing gets a public address or open ingress without approval.
  • Changes above 2000 USD a month need approval; when on is true, non-production applies after checks.

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.

Infrastructure Agent · Banking | Basinwright Industries