--- title: AWS Cloud Adoption Framework (CAF) in Practice: MAP, Landing Zones, and Well-Architected description: CAF 3.0 organizes six perspectives and 47 capabilities—up from 31 in CAF 2.0—plus four phases (Envision, Align, Launch, Scale). Here is how to connect those workshops to Control Tower, MAP, and Well-Architected without treating the framework as a slide deck. url: https://www.factualminds.com/blog/aws-cloud-adoption-framework-practice-map-well-architected/ datePublished: 2026-05-14T00:00:00.000Z dateModified: 2026-06-10T00:00:00.000Z author: palaniappan-p category: Cloud Architecture tags: aws-migration, aws-organizations, cloud-governance, map, well-architected, cloud-adoption-framework, aws --- # AWS Cloud Adoption Framework (CAF) in Practice: MAP, Landing Zones, and Well-Architected > CAF 3.0 organizes six perspectives and 47 capabilities—up from 31 in CAF 2.0—plus four phases (Envision, Align, Launch, Scale). Here is how to connect those workshops to Control Tower, MAP, and Well-Architected without treating the framework as a slide deck. The [AWS Cloud Adoption Framework (AWS CAF)](https://aws.amazon.com/cloud-adoption-framework/) is how AWS packages lessons from large-scale customer transformations into **six perspectives** and, as of **CAF 3.0**, **47 discrete capabilities**—**up from 31** in version 2.0. Jeff Barr announced CAF 3.0 on **November 23, 2021**, emphasizing four transformation domains (Technology, Process, Organization, Product) and four iterative phases: **Envision**, **Align**, **Launch**, and **Scale** ([AWS News Blog, Nov 23, 2021](https://aws.amazon.com/blogs/aws/aws-cloud-adoption-framework-caf-3-0-is-now-available/)). The overview whitepaper’s publication date is **November 22, 2021** ([AWS CAF overview](https://docs.aws.amazon.com/whitepapers/latest/overview-aws-cloud-adoption-framework/welcome.html)). This article is for executives, enterprise architects, and platform leads who already know the CAF posters exist but need a **practical** link between CAF and the programs you actually fund: **landing zones** (often via **AWS Control Tower**), the **Migration Acceleration Program (MAP)**, and **AWS Well-Architected** reviews. It is not a Control Tower click path—use our [Control Tower setup guide](/blog/how-to-set-up-aws-control-tower-multi-account-governance/) for that. > **Need hands-on delivery?** [AWS migration consulting](/services/aws-migration/) and [AWS managed services](/services/aws-managed-services/) engagements from an AWS Partner can anchor MAP phases to your CAF backlog. ## What CAF is (and is not) CAF is **not** a migration runbook. It is a **stakeholder model**: - **Business** — outcomes, investment, value measures - **People** — skills, org design, culture - **Governance** — portfolio, risk, compliance, FinOps hooks - **Platform** — landing zone, hybrid connectivity, shared services - **Security** — identity, data protection, detection, IR readiness - **Operations** — observability, incident management, capacity **CAF 3.0** explicitly expands from **31 to 47** capabilities so digital transformation and analytics-driven operations have room on the same roadmap as migration ([same Nov 23, 2021 announcement](https://aws.amazon.com/blogs/aws/aws-cloud-adoption-framework-caf-3-0-is-now-available/)). ## From CAF phases to funded work | CAF phase | Plain-English outcome | Typical AWS programs | | ------------ | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Envision** | Align leadership on why cloud + what “good” looks like | Executive workshop; **AWS Cloud Maturity Assessment** (CMA) as a structured baseline ([public-sector overview](https://aws.amazon.com/blogs/publicsector/operationalizing-cloud-adoption-with-the-aws-cloud-maturity-assessment/)) | | **Align** | Gap analysis, priorities, owners, **quarterly** milestones | CMA results + MAP **Assess** deliverables; portfolio governance | | **Launch** | Pilots in production with measured value | Landing zone hardening; MAP **Mobilize** foundations | | **Scale** | Repeatable factory + continuous improvement | MAP **Migrate & Modernize** waves; automated **Well-Architected** cycles | AWS states the CMA uses **77 stakeholder-driven questions** across the six perspectives and scores maturity on **five levels** from _initial_ to _optimized_ ([AWS Public Sector Blog, operationalizing CMA](https://aws.amazon.com/blogs/publicsector/operationalizing-cloud-adoption-with-the-aws-cloud-maturity-assessment/)). That is the closest thing AWS publishes to an “objective spreadsheet” for Align—use it before buying more governance SKUs. ## MAP: the migration engine that plugs into Launch MAP is documented as a **three-phase** methodology: **Assess**, **Mobilize**, and **Migrate & Modernize**—with tooling, training, partner engagement, and financial mechanisms described on [AWS MAP](https://aws.amazon.com/migration-acceleration-program/) and in service-specific guides such as [MAP tagging under AWS Transform](https://docs.aws.amazon.com/transform/latest/launchguide/map.html). **Opinionated take:** treat **MAP Mobilize** as the funding and accountability wrapper for the **Platform + Security** capabilities you need before wave migrations—not as “the month we install Control Tower.” If Mobilize completes without a written standard for VPC patterns, identity propagation, and tag enforcement, **Migrate & Modernize** becomes rework. AWS markets directional outcomes for MAP participants (for example **~31% average infrastructure cost savings**, **~62% more efficient IT ops management**, and **~69% fewer unplanned downtime events** on their MAP overview page). Treat those figures as **AWS-reported portfolio statistics**, not a guarantee for your workload—your Assess phase exists to replace averages with **your** TCO model. ## Landing zones and Control Tower — Platform, not “the whole framework” Control Tower implements guardrails and account vending on top of **AWS Organizations**. That is squarely **Platform** work with **Governance** and **Security** prerequisites (OU design, SCP strategy, log archive account). > **What broke** — A team deployed **Control Tower** with default OUs, then Finance required **CostCenter** tags for chargeback. Tag policies were added late; every service pipeline needed emergency exceptions because sandbox accounts predated the mandatory keys. Rollback was messy because production workloads had already landed in the “wrong” OU path. Fix: pause deployments, run Align again, remap OUs with **exception** accounts codified—not ad-hoc. ## Well-Architected — the workload lens after the platform exists After the landing zone can support standard logging, backups, and identity patterns, run [AWS Well-Architected](/blog/aws-well-architected-framework-6-pillars-explained/) reviews on **pilot** workloads during **Launch/Scale**. CAF without Well-Architected becomes strategy without design feedback; Well-Architected without CAF becomes isolated heroics that do not scale. ## What to do this week 1. Download the [**AWS CAF overview** PDF](https://docs.aws.amazon.com/whitepapers/latest/overview-aws-cloud-adoption-framework/overview-aws-cloud-adoption-framework.pdf) and mark which of the **47** capabilities are **out of scope** for the next 12 months—explicit “won’t do” is as valuable as “must do.” 2. Run—or re-run—the **Cloud Maturity Assessment** and attach owners to the **bottom three** maturity scores by perspective. 3. Map your **MAP** phase (if applicable) to CAF **Align/Launch** deliverables on one slide; if the slide does not work, your PMO and partner are misaligned. 4. Schedule **Well-Architected** only for workloads that already inherit central logging and SSO from the landing zone. ## Reproduce this baseline reading > **Reproduce this** — Start from the authoritative **[AWS CAF overview whitepaper](https://docs.aws.amazon.com/whitepapers/latest/overview-aws-cloud-adoption-framework/welcome.html)** (publication **November 22, 2021**; links localized PDFs). Pair it with the **[CAF 3.0 announcement](https://aws.amazon.com/blogs/aws/aws-cloud-adoption-framework-caf-3-0-is-now-available/)** for the **47** capability count and four phases. For MAP mechanics (including tagging expectations), use **[MAP in the AWS Transform launch guide](https://docs.aws.amazon.com/transform/latest/launchguide/map.html)**. ## What this post does not cover - Step-by-step **Control Tower** installation (see the [dedicated guide](/blog/how-to-set-up-aws-control-tower-multi-account-governance/)). - **Industry-specific** regulatory playbooks (FSI, healthcare) beyond pointing at CAF Security capabilities—you still need legal interpretation. - **SAP** or large ERP migration-specific CAF tailoring. - **Partner contracts** or MAP funding negotiation—your AWS account team and authorized partner own those terms. --- **If you only do one thing:** Complete **Align** with named owners on **three** capability gaps surfaced by CMA or MAP Assess **before** you expand account vending or migration waves. Operationalize the CoE with our [AWS Cloud Center of Excellence operating model](/blog/aws-cloud-center-of-excellence-operating-model-2026/) guide. ## FAQ ### Is the AWS CAF the same as a landing zone project? No. CAF is an organizational roadmap across Business, People, Governance, Platform, Security, and Operations. A landing zone is a technical outcome—accounts, networking, identity, logging—usually owned by the Platform and Security perspectives. You can stand up a landing zone without CAF, and you can run CAF workshops without delivering a landing zone; the best results come when Align-phase capability gaps explicitly fund the landing-zone backlog. ### When should we skip formal CAF workshops? If you already executed a recent Cloud Maturity Assessment (CMA) with executive sponsorship, published a prioritized capability backlog, and have a single owner for the transformation roadmap, repeating CAF Envision/Align may not buy much. You still benefit from the CAF vocabulary for gap analysis—but another facilitator-led workshop is overhead. Early-stage startups with one account and no regulated-data mandate may defer structured CAF until multi-account scale or compliance pressure appears. ### What goes wrong if we treat CAF as documentation only? Teams download the CAF overview PDF, map buzzwords to existing projects, and never close Governance or People gaps. Common failure mode: **Platform** delivers Control Tower while **Governance** never aligns OUs to finance chargeback keys—six months later tag policies block every deployment. Another: **Security** mandates controls that **Operations** cannot run because observability and incident runbooks were out of scope for Launch. ### How does MAP relate to CAF? MAP is a three-phase migration program (Assess → Mobilize → Migrate & Modernize) with funding and partner mechanics documented under AWS Transform / MAP guidance. CAF phases are broader (Envision → Align → Launch → Scale) and cover digital transformation beyond migration. In practice, MAP Mobilize usually overlaps CAF Launch capabilities for landing zone and security baseline; MAP Assess outputs feed CAF Align gap analysis. Your partner engagement should spell out which MAP phase aligns to which CAF capabilities so finance and engineering share one timeline—see our [MAP SMB guide](/blog/aws-migration-acceleration-program-map-smb-guide/) for how funding gates work. ### Where does Well-Architected fit? Well-Architected reviews evaluate workload architecture against six pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability). CAF **Platform** and **Security** capabilities set the organizational prerequisites (standards, pipelines, observability baselines) that make workload reviews repeatable. Run Well-Architected on pilot workloads during CAF Launch/Scale—not as a substitute for fixing multi-account governance gaps first. ### Do we need AWS Professional Services to use CAF 3.0? No. The CAF overview whitepaper and prescriptive guidance are public; your AWS account team or an AWS Partner can facilitate workshops. The risk without experienced facilitators is workshop theater: sticky notes with no funded backlog. If your partner cannot tie every capability gap to an owner, metric, and quarter, pause until they can. --- *Source: https://www.factualminds.com/blog/aws-cloud-adoption-framework-practice-map-well-architected/*