Skip to content
ValidatedAWS Competency

Cloud Operations Competency

Validated for operating what we build — observability, incident practice, cost management, and the guardrails that keep an estate compliant after handover.

Status
Validated
Reviewed
June 2026
Renews
June 2028
References
2 submitted

What it covers

The part that starts after go-live.

Operational maturity is assessed separately from architecture. AWS examines whether a partner can run an estate reliably and hand it over in a state the client can operate.

Observability

Metrics, structured logging, and tracing wired before the first user lands.

Incident practice

On-call rotations, escalation paths, and rehearsed incident scenarios.

Cost management

Tagging, allocation, and a monthly FinOps rhythm the client team runs.

Compliance guardrails

Config rules and service control policies that block drift before it lands.

Validation criteria

What AWS assessed.

Cloud Operations validation focuses on evidence of sustained operation — dashboards, incident records, and post-handover client capability.

How validation works

Operational tooling

Monitoring, alerting, and runbooks demonstrated across live accounts.

Met

Incident evidence

Real incident records with detection time, response, and follow-up actions.

Met

Cost discipline

Allocation coverage and demonstrated optimisation across client estates.

Met

Handover capability

Clients operating the platform independently after enablement.

Met

Services

What we build it on.

  • CloudWatch
  • X-Ray
  • Systems Manager
  • Config
  • Control Tower
  • Cost Explorer

Team on this practice

Nine people across cloud and security, with the on-call practice shared between studio ventures and client engagements.

Work with this practice

Need someone to run it properly?

Discovery comes first — a short, bounded review that ends in an architecture, a scope, and a price. You keep the output either way.