Cloud architecture consulting

Production platforms accumulate account sprawl, implicit trust paths and undocumented failure domains. This engagement reviews the current state against provider documentation and writes the decisions that are still missing.

Who this engagement is for

Cloud architects, platform engineers and engineering leaders who already run production workloads and need a written review of landing-zone, identity, networking or reliability decisions.

Information required to begin

  • Provider list and primary regions in use
  • Account, subscription or project hierarchy (Organizations, management groups, folders or Resource Directory)
  • Identity model (SSO, IAM roles, workload identity)
  • Network topology (VPC/VNet, hubs, private endpoints, egress)
  • Reliability targets (RTO/RPO) and last failover test date if any
  • 90 days of billing export if cost is in scope

Engineering process

  1. Consultation to confirm scope and the decision you need to make
  2. Document and diagram review against current provider docs. Missing diagrams shrink the review rather than being filled in
  3. Well-Architected, Cloud Adoption Framework or equivalent used as a question set, not as a scored maturity percentage
  4. Working session with the platform or architecture owner
  5. Written findings, ADRs and a prioritized risk register

Deliverables

  • Current-state assessment
  • Target architecture notes
  • Architecture decision records for the scoped decisions
  • Risk register with owner and residual risk

Provider-specific scope

  • AWS Organizations, Control Tower and landing-zone patterns as documented by AWS
  • Azure management groups and Cloud Adoption Framework landing zones
  • Google Cloud resource hierarchy and landing-zone design docs
  • Alibaba Cloud Resource Directory where that is the production control plane

Limitations

  • We do not implement changes in your accounts unless a separate implementation phase is agreed.
  • Findings depend on the access and diagrams you provide. Missing billing or IAM exports limit the review.
  • We are not an AWS, Azure, Google Cloud or Alibaba Cloud partner and do not replace vendor support.

What is not included

  • 24x7 operations or on-call coverage
  • Application code changes
  • Guaranteed cost savings
  • Official provider certifications presented as a product of this engagement

Author

Written by Ankit Mehta. Methods used in this engagement are documented in the related guides below.

Related technical guides