UAE · ENBook a demo
RetailEngineeringAssistant

Infrastructure Agent

Provisions and maintains cloud infrastructure.

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

It provisions and maintains the cloud infrastructure for the online store, commerce services and data platform, and the edge infrastructure in stores (store servers, networks, till connectivity), as code. It plans each change, scales capacity ahead of sale events and opens the change for review.

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 cloud and store infrastructure inventory: the current resources, capacity, store edge estate and last year's peak load for the services named..

  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 Platform with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens the infrastructure-as-code change with its plan and rollout. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The infrastructure guide: the infrastructure-as-code repository, environments, network and PCI DSS segmentation, the store edge estate, the scaling plans for sale events and the tagging rules.

Reads from

the cloud and store infrastructure inventory: the current resources, capacity, store edge estate and last year's peak load for the services named.

Acts in

the code repository: it opens the infrastructure-as-code change with its plan and rollout.

Hands back

An object with plan_summary, resources (a list of resource, action and environment), rollout (a list of batch, stores and start_time), cost_change_per_month and pull_request_description.

Asks a person when

The change touches the card data environment or store tills, or decommissions anything in production.

ApproverHead of Platform

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Capacity headroom for sale events (%)50Capacity for a sale event is last year's peak plus this.
Stores changed per batch25Store edge changes roll out in batches of this many stores.
Store changes only after (local time)22:00Store edge changes start only after the store closes.
Require cost tagsOnWhen on, every resource carries team and service tags.

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

Rules it always follows

  • All changes are made as code and reviewed; no manual console changes.
  • Keep the card data environment segmented from the rest of the network (PCI DSS); a change crossing that boundary needs the approver.
  • Scale for a sale event to last year's peak plus 50 percent, tested before the event.
  • Change store edge systems in batches of 25 stores, only after 22:00 local time.
  • When on is true, every resource carries team and service tags.

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 · Retail | Basinwright Industries