Keep one cutover record everyone can follow
During a migration window, conflicting status reports create avoidable risk. Record the current phase, evidence and decision owner in one shared run log.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
90 articles in Cloud solutions
Page 3 of 5
Diagnose a platform policy failure at its effective scope
A workload can inherit several layers of control. Identify which rule applies to the actual identity and resource before changing permissions.
Read articleThe restore completed but the application will not start
Diagnose compatibility and dependencies before repeating the restore. A successful data job can leave the application missing configuration, keys or a usable identity.
Read articleConfirm write authority before changing regional traffic
During an outage, reachable does not necessarily mean safe to use. Establish which data path is authoritative before directing customers to it.
Read articleDo not let the next apply undo incident containment
Before resuming deployments, compare emergency cloud changes with the checked-in definition. Preserve the intended protection through a reviewed reconciliation.
Read articleStop exposure before investigating the release in depth
When a candidate is harming users, use the tested control to limit further impact. Preserve enough evidence to understand what already happened.
Read articleA service objective is burning. Find the affected journey
Start with the operations behind the signal, then use infrastructure evidence to locate the cause. The objective tells you about impact, not automatically the failing component.
Read articleA team's cloud cost jumped. Check the basis before the workload
A higher allocated total can come from usage, pricing, currency, credits or changed rules. Separate those causes before asking engineers to remove resources.
Read articleNew connections fail after a rotation
Existing sessions can hide a stale credential until the pool reconnects. Compare target validity, secret version and consumer refresh before rotating again.
Read articleMove a coherent capability before moving every endpoint
A phased migration works best when traffic and data ownership share a clear boundary. Choose a slice that can operate and recover independently.
Read articleApply a new cloud baseline to existing workloads gradually
A policy that works for a fresh environment can disrupt older services. Discover dependencies and test the effective change before broad enforcement.
Read articleKeep older recovery points usable after an application release
A schema or encryption change can make retained backups harder to use. Test recovery across the release boundary before retiring compatible code and keys.
Read articleFailback is another data migration
Once the recovery region accepts changes, the original region is no longer automatically current. Reconcile and transfer authority before returning traffic.
Read articleBring existing resources under code without recreating them
Adopting an unmanaged resource requires a matching definition and a reviewed plan. Registration alone does not prove that the next apply will preserve it.
Read articleKeep the stable release compatible with canary writes
A small rollout still changes shared data. Separate incompatible schema and behaviour changes so the stable application remains a usable recovery path.
Read articleRun the new indicator beside the old one before switching alerts
A measurement change can alter the reliability story without changing the service. Compare definitions and known failures before moving operational decisions to it.
Read articleChange allocation rules without rewriting history silently
A new ownership or shared-cost policy can move reported spend between teams. Publish its effective date and comparison before using it for decisions.
Read articleMove from embedded credentials before automating rotation
Consumers must retrieve or receive updates through a maintained path. Scheduling rotation first can break applications that still depend on a copied value.
Read article