Depth 06.3 · Managed services · Level 3
Infrastructure care
Infrastructure care is the scheduled maintenance of the servers, cloud accounts, databases and networks a product runs on. It covers patching, backups that are restored in tests, certificate and dependency renewals, access reviews and cost checks. None of it is visible when done well, which is why it is often skipped.
Specification
- Input
- Administrative access to the cloud accounts and hosts in scope, and a list of what may be changed without asking first.
- Method
- We keep a maintenance calendar, apply patches in a test environment before production, restore a backup on a fixed schedule to prove it works, and review who has access to what.
- Deliverable
- A maintenance calendar, a backup restore record, an access review record and a monthly cost note.
- Measured by
- Patches applied within the window set in your contract, backup restores that succeeded, and expired certificates or credentials, which should be zero.
Most often bought inProfessional services, Logistics and supply chain
The artefact, before and after
A maintenance calendar, a backup restore record, an access review record and a monthly cost note.
Inside it
- 01Operating system and dependency patching
- 02Backups with scheduled restore tests
- 03Certificate and domain renewals
- 04Access reviews
- 05Cloud cost review
Typical first engagement
The usual order of a first piece of work. Timing and price are set at scoping, once we have seen the stack.
- 01InventoryYou get: Hosts, services, versions, certificates and renewal dates in one list.
- 02Patch planYou get: Out of date components ranked by exposure, with an update order.
- 03Monthly routineYou get: Patching, backup restore tests and access review on a schedule.
Managed services
Next in this line
Ask about this part of the stack
Write one question about infrastructure care in your own systems. We answer it in writing and name what we would need to see to answer it properly.
A written reply, no call needed.