Migration
Assessing which workloads should move first
Choose early cloud migration workloads by screening readiness, comparing business value and risk, and selecting a useful first move group.
Archive
Migration
Choose early cloud migration workloads by screening readiness, comparing business value and risk, and selecting a useful first move group.
Cost Control
Assign direct cloud charges, document shared-cost rules and give teams statements they can review and reconcile.
Governance
Map cloud account and workload owners to decision rights, daily operations, budget contacts and escalation routes.
Migration
Map application connections, data flows and shared services so you can choose migration groups and identify cross-environment risks.
Reliability
Calculate database connections across app instances and test pool waits, errors and query latency before launch.
Governance
Check export methods, formats, access windows, charges and deletion terms before committing data to a cloud supplier.
Cloud Planning
Shortlist a cloud region using user latency, dependent services, service availability, data handling and operating capacity.
Migration
Choose a migration rollback path based on traffic, write ownership and data state, then set decision triggers and rehearse both fallback branches.
Reliability
Decide which cloud signals deserve an alert by defining impact, owner, urgency and the operator's next step.
Reliability
Define checkable cloud requirements from business availability, recovery targets, data sensitivity and handling needs.
Cost Control
Use read frequency, retrieval time and retention to choose object-storage tiers, then check total lifecycle and recovery costs.
Cost Control
Build a consistent cloud cost view, assign charges to workloads, investigate changes and reconcile internal reports with the final bill.
Cloud Planning
Plan a cloud deployment workflow with release stages, environment checks, a controlled rollout and a response to failure.
Cloud Planning
Choose cloud compute by comparing application constraints, operating responsibility, demand, total cost and region fit.
Identity
Plan cloud access for staff, administrators and workloads with narrow permissions, protected sign-in and a reviewable removal process.
Cloud Planning
Plan cloud infrastructure around workloads, data, reliability and operating responsibilities before choosing a deployment approach.
Migration
Plan a cloud migration by choosing workload treatments, grouping dependencies, sequencing waves and defining cutover and fallback checks.
Reliability
Build cloud monitoring around user outcomes, diagnostic signals and alerts that lead to a clear response.
Cloud Planning
Cloud networking connects users, offices and workloads to services through defined routes, names and access controls.
Governance
Set up cloud operations governance with clear workload ownership, operating rules, evidence reviews and a way to resolve exceptions.
Reliability
Define cloud reliability for business workloads, choose controls for likely failures, and check whether recovery meets agreed targets.
Cost Control
Review charged resources, compute size, operating hours and commitments against workload needs and actual billing.
Governance
Assign owners and evidence for exposure changes, cloud server updates, deployment secrets and suspected account compromise.
Cloud Planning
Choose cloud storage by workload and access needs, then design protected backups and check recovery against business targets.
Governance
Assess cloud service terms, support, data handling, exit routes and feature readiness before approving a vendor arrangement.
Cost Control
Build a fair cloud compute estimate using workload scenarios, billing units, storage and data transfer.
Cloud Planning
Compare RDS, Cloud SQL, Azure PostgreSQL, MongoDB Atlas and BigQuery against workload needs and documented limits.
Identity
Public and private access describe the network path to an application, not whether its users are trusted.
Reliability
Compare what redundancy and recovery each protect, where their limits differ, and how to combine them against business targets.
Cost Control
Compare AWS, Azure and Google Cloud commitments using eligible demand, matching rules and a lower-use cost case.
Migration
Compare AWS, Azure and Google Cloud support by severity, initial response, hours, escalation and the work your team must do.
Cloud Planning
An office-to-cloud connection should be designed around the applications staff need, not a blanket path to every cloud address.
Reliability
Define availability around a business journey, choose a useful measure, and record recovery targets alongside the objective.
Identity
Build cloud roles from required tasks, resource scope and duration, then check the grant and its holder's other access.
Cloud Planning
Verify whether a promised cloud feature is released, supported and usable in the intended region, plan and account.
Identity
Handoff a suspected cloud account compromise, preserve available evidence and coordinate containment and reporting decisions.
Cost Control
Build a managed-database cost estimate from running capacity, storage, backups, transfers and the right query billing model.
Cost Control
Trace billable idle cloud resources to their owners and purpose before stopping or deleting VMs, disks and addresses.
Identity
Keep credential values out of deployment files, review leak paths and respond if a real secret is committed.
Cloud Planning
Choose a managed cloud database by workload, operational responsibility, recovery needs, connection capacity and cost.
Reliability
Plan cloud server patch priorities and deployment waves, then verify application health and track skipped or failed machines.
Identity
Give applications owned identities, choose supported authentication, limit runtime access and retire identities with their workloads.
Migration
Map business actions, components, data and owners before migration so placement decisions rest on a usable workload inventory.
Reliability
Read request latency with traffic, errors, dependencies and server resources to investigate slow application actions.
Cloud Planning
Compare object, block and file storage by access method, sharing needs and application behaviour before choosing a cloud service.
Cloud Planning
Transfer cloud operations from an external provider with a service inventory, usable runbooks, checked procedures and controlled access removal.
Reliability
Set a database restore test pass condition, isolate the restored copy and measure data and application recovery.
Cloud Planning
DNS changes are deployment changes because they determine which service clients reach.
Reliability
Prepare a regional disruption plan with clear failover criteria, independent dependencies, data decisions and a tested return path.
Cloud Planning
Compare public cloud, private infrastructure and combined setups by operating work, workload fit, data placement and recovery needs.
Cost Control
Reconcile the billed total, inspect service charges and billing units, and keep shared or unassigned workload costs visible.
Governance
Trace cloud infrastructure changes through configuration review, current plans and deployment records while protecting state and secrets.
Reliability
Choose application log events, fields, identifiers and safeguards that help operators reconstruct an incident.
Identity
Find cloud credentials that appear unused, check dependencies, disable and observe them, then delete confirmed dormant credentials.
Reliability
Use an incident timeline to find duplicate, mistimed and unactionable alerts while preserving useful detection.
Reliability
Review backup coverage, job history and restore exercises against each workload's recovery requirements, then assign gaps.
Reliability
Trace a cloud access change to its affected service, assess reachability and record the correction and checks.
Identity
Identify privileged cloud grants, confirm each business need and close retain, reduce or remove decisions with platform limits in view.
Governance
Read a cloud SLA's coverage, conditions, exclusions, credits and claim process before signing a service agreement.
Cost Control
Measure busy workload demand, screen compute sizes and check application results before treating a resize as a saving.
Reliability
Decide how to respond to a faulty application release by checking version, traffic and data compatibility before verifying live service.
Cost Control
Set operating windows for development and test resources, check provider stop behaviour and observe a full start-stop cycle.
Reliability
Set boundaries for cloud development, test and production while keeping test results relevant to a live release.
Cost Control
Classify purchases, recurring charges, usage and adjustments, then compare billable units to investigate a cloud cost increase.
Reliability
Choose release checks around changed components, important user actions and explicit pass conditions before changing live services.
Reliability
Test the full recovery path, measure actual RTO and RPO, inspect recovered data, and record the limits of each exercise.
Reliability
Plan an isolated cloud-backup restore, measure usable recovery against RTO and RPO, and record what the test actually proves.
Reliability
When one cloud service cannot reach another, locate the failing layer before changing rules.
Cloud Planning
Compare VMs and managed application hosting by OS control, application compatibility, scaling and operating responsibility.