This chapter covers the AWS Cloud Adoption Framework (CAF), a key concept tested in Domain 1: Cloud Concepts of the CLF-C02 exam. Understanding CAF is essential because it provides a structured approach to cloud adoption, helping organizations align their business goals with technical capabilities. This objective carries approximately 8-10% of the exam weight, so mastering it is critical for your certification. By the end of this chapter, you will understand the six CAF perspectives, their capabilities, and how they guide cloud migration and transformation.
Jump to a section
Imagine you want to build a house. You have a vision, but you don't know where to start. You hire an architect who follows a structured framework: first, they understand your business needs (like number of rooms, budget), then they create blueprints (strategy), design the structure (design), and finally oversee construction (implementation). But they also plan for future moves (migration), ensure the house runs smoothly (operations), and keep it secure (security). The architect doesn't just build; they guide you through every phase, ensuring your house is efficient, scalable, and aligned with your goals. Similarly, the AWS Cloud Adoption Framework (CAF) is a structured guide that helps organizations plan and execute their cloud adoption journey. It provides best practices and guidance across six perspectives: Business, People, Governance, Platform, Security, and Operations. Just as an architect tailors the house to your needs, CAF helps you align your cloud strategy with your business objectives, identify gaps, and build a roadmap. It's not a tool but a framework—a set of principles and actions to reduce risk and accelerate cloud adoption. Without it, you might build a house with missing rooms or weak foundations; with CAF, you have a proven blueprint for success.
What is the AWS Cloud Adoption Framework (CAF)?
The AWS Cloud Adoption Framework (CAF) is a comprehensive set of best practices and guidance designed to help organizations build a cloud adoption strategy, identify gaps in their capabilities, and create a roadmap for successful cloud migration. It was developed by AWS based on lessons learned from thousands of cloud adoptions. The CAF is not a tool or service; it is a framework that provides a structured approach to cloud adoption, reducing risk and accelerating outcomes.
The problem CAF solves is that cloud adoption is not just about technology; it involves people, processes, and business changes. Many organizations fail because they focus only on technical aspects, ignoring organizational readiness, governance, or security. CAF addresses this by dividing cloud adoption into six perspectives, each covering specific areas of concern.
How CAF Works: The Six Perspectives
CAF organizes its guidance into six perspectives, each representing a stakeholder group or area of focus:
Business Perspective: Ensures that cloud investments align with business goals. It helps create a business case, manage finances, and measure outcomes. Key capabilities include IT finance, strategy, and benefits realization.
People Perspective: Focuses on the human side—training, change management, and organizational culture. It helps develop cloud-ready teams and roles. Key capabilities include resource management, incentive management, and training.
Governance Perspective: Provides processes to manage cloud resources, ensure compliance, and control costs. It includes portfolio management, risk management, and policy enforcement.
Platform Perspective: Covers the technical architecture—how to design, implement, and optimize cloud infrastructure. It includes application design, data management, and platform architecture.
Security Perspective: Ensures data confidentiality, integrity, and availability. It includes identity and access management, detective controls, and incident response.
Operations Perspective: Focuses on running the cloud environment day-to-day—monitoring, incident management, and service continuity. It includes operations management, event management, and problem management.
Each perspective has a set of capabilities that describe the skills and processes needed. CAF provides a maturity model to assess current state and identify gaps.
CAF Phases and Actions
CAF organizes cloud adoption into four phases:
Envision: Define business objectives and align cloud strategy. Actions include creating a business case and identifying stakeholders.
Align: Assess current capabilities and identify gaps across the six perspectives. Actions include conducting a readiness assessment and developing a transformation roadmap.
Launch: Execute the roadmap by implementing pilot projects or full migrations. Actions include building foundational environments and deploying workloads.
Scale: Expand successful pilots to broader adoption, optimize costs, and improve operations. Actions include automating processes and scaling governance.
Comparison to Other Frameworks
CAF is often compared to the AWS Well-Architected Framework, but they serve different purposes. Well-Architected focuses on designing secure, high-performing, resilient, and efficient architectures for existing workloads. CAF focuses on the entire cloud adoption journey, including organizational change. While Well-Architected is technical, CAF is strategic and includes business and people aspects.
When to Use CAF vs Alternatives
Use CAF when you are starting your cloud journey or planning a large-scale migration. It is ideal for creating a roadmap and assessing readiness. For ongoing optimization of existing architectures, use the Well-Architected Framework. For specific compliance needs, use AWS Artifact or AWS Config. CAF is not a technical implementation tool; it is a strategic planning framework.
Key Capabilities and Examples
Each perspective includes specific capabilities. For example, under the Security Perspective, one capability is "Identity and Access Management" which includes implementing least privilege. Under the Operations Perspective, "Event Management" includes setting up Amazon CloudWatch alarms. The CAF provides detailed action plans for each capability.
Pricing
CAF itself is free—it is documentation and guidance. However, the assessments and tools you use (like AWS Cloud Adoption Readiness Tool) are also free. The cost comes from the actual AWS services you implement based on the roadmap.
Exam Relevance
CLF-C02 tests your understanding of the six perspectives and their purpose. You may be asked to identify which perspective addresses a specific concern (e.g., cost management belongs to Business Perspective). You should know the four phases and the difference between CAF and Well-Architected Framework.
Envision Phase: Define Objectives
In this first phase, stakeholders articulate business goals and identify how cloud adoption can support them. For example, a retail company might want to reduce time-to-market for new features. The team creates a business case outlining expected benefits, costs, and risks. They also identify key performance indicators (KPIs) like cost savings or agility. AWS recommends involving executives from business, finance, and IT to ensure alignment. This phase typically takes a few weeks and results in a signed-off cloud strategy document.
Align Phase: Assess Readiness
The organization assesses its current capabilities against the six CAF perspectives using the AWS Cloud Adoption Readiness Tool (CAR). For each perspective, they score maturity from 1 (initial) to 5 (optimizing). For example, under People perspective, they might find they lack cloud training. The output is a gap analysis showing where improvements are needed. This phase takes 2-4 weeks and produces a transformation roadmap with prioritized actions.
Launch Phase: Implement Pilot
Based on the roadmap, the team selects a low-risk workload for migration, such as a non-critical web application. They set up a landing zone using AWS Control Tower or AWS Organizations to establish governance. They migrate the workload using AWS Migration Hub or AWS Server Migration Service. During this phase, they also train staff and update processes. The pilot typically takes 1-3 months and validates the approach before scaling.
Scale Phase: Expand Adoption
After a successful pilot, the organization scales by migrating additional workloads using repeatable patterns. They automate deployment with AWS CloudFormation and improve monitoring with Amazon CloudWatch. They also optimize costs using AWS Cost Explorer and rightsizing. Governance is automated with AWS Config rules. This phase is ongoing and focuses on continuous improvement. Key metrics include migration velocity and cost savings.
Ongoing: Operate and Optimize
Once workloads are running, the organization enters the operate phase, which is part of the Operations perspective. They use AWS Systems Manager for patching, AWS Trusted Advisor for best practice checks, and AWS Well-Architected Tool for reviews. They continuously assess against CAF perspectives to identify new gaps. This phase ensures the cloud environment remains secure, cost-effective, and aligned with business goals.
Scenario 1: Large Enterprise Migrating from On-Premises
A global manufacturing company with thousands of servers wants to migrate to AWS to reduce data center costs. They use CAF to structure their approach. In the Envision phase, they define a goal: reduce infrastructure costs by 30% over two years. In Align, they assess their capabilities and find they lack cloud security expertise (Security perspective gap). They hire a cloud security architect and train their operations team. In Launch, they migrate a non-critical inventory system using AWS Application Migration Service. During Scale, they migrate 200 applications over 18 months, leveraging AWS Organizations for governance and AWS CloudFormation for automation. They save 35% on costs. A common mistake is skipping the People perspective, leading to resistance from staff. By using CAF, they proactively addressed training and change management, ensuring smooth adoption.
Scenario 2: Startup Building a New Cloud-Native Application
A fintech startup wants to build a new application entirely on AWS. They use CAF to ensure they start with proper governance and security. In Envision, they define agility as their primary goal—ability to release features weekly. In Align, they assess their small team and find gaps in operations (no incident response plan). They implement Amazon CloudWatch alarms and AWS Lambda for automated remediation. In Launch, they build a serverless architecture using AWS Lambda, Amazon API Gateway, and Amazon DynamoDB. They use AWS Cloud Development Kit (CDK) for infrastructure as code. In Scale, they expand to multiple regions for disaster recovery. Cost is managed using AWS Budgets. Without CAF, they might have neglected governance, leading to security breaches. CAF helped them prioritize security and operations from day one.
Scenario 3: Government Agency Requiring Compliance
A government agency needs to migrate workloads to AWS while meeting strict compliance standards (e.g., FedRAMP). They use CAF to map their compliance requirements to the Security and Governance perspectives. In Align, they identify gaps in logging and access control. They implement AWS CloudTrail, AWS Config, and AWS Identity and Access Management (IAM) with least privilege. They also use AWS Artifact to access compliance reports. In Launch, they migrate a low-impact system first. They use AWS Control Tower to enforce guardrails. Misconfiguration of IAM policies is a common issue; CAF's Security perspective provides guidance on identity management. The agency successfully achieves compliance and reduces audit preparation time by 50%.
What CLF-C02 Tests on CAF
The exam tests your understanding of the six CAF perspectives and their purpose. You will not be asked to memorize every capability but to identify which perspective addresses a given concern. For example, a question might ask: 'Which CAF perspective focuses on managing cloud costs?' The answer is Business perspective. Another common question: 'Which phase involves creating a business case?' Answer: Envision.
Common Wrong Answers and Why
Confusing CAF with Well-Architected Framework: Many candidates think CAF is about technical architecture. Wrong. CAF is broader, covering business, people, and governance. Well-Architected is purely technical.
Mixing up perspectives: For example, attributing cost management to Governance instead of Business. Cost management is a business concern, not a governance one (governance focuses on policies and compliance).
Thinking CAF is a tool: CAF is a framework, not a service. AWS does not have a 'CAF service' you subscribe to.
Misidentifying phases: Some think 'Align' is about migration execution. Actually, Align is about assessment and planning; execution happens in Launch.
Specific Terms and Values
Six perspectives: Business, People, Governance, Platform, Security, Operations.
Four phases: Envision, Align, Launch, Scale.
AWS Cloud Adoption Readiness Tool (CAR) – used in Align phase.
Capabilities: Each perspective has multiple capabilities (e.g., under Security: Identity and Access Management, Detective Controls, Infrastructure Security, Data Protection, Incident Response).
Tricky Distinctions
Business vs. Governance: Business is about strategy and finance; Governance is about policies and compliance. For example, creating a budget is Business; setting a policy that requires approval for budget changes is Governance.
Platform vs. Operations: Platform is about design and implementation; Operations is about day-to-day management. For example, choosing a database type is Platform; monitoring database performance is Operations.
Decision Rule for Multi-Choice
When a question asks which perspective addresses a specific concern, think about the stakeholder:
If it's about money or strategy → Business.
If it's about people and training → People.
If it's about rules and compliance → Governance.
If it's about technical design → Platform.
If it's about security → Security.
If it's about running and monitoring → Operations.
Use this elimination strategy to narrow down options.
CAF has six perspectives: Business, People, Governance, Platform, Security, Operations.
The four CAF phases are Envision, Align, Launch, and Scale.
CAF is a framework, not a tool or service.
The Business perspective covers cost management and strategy.
The People perspective focuses on training and change management.
The AWS Cloud Adoption Readiness Tool (CAR) is used in the Align phase.
CAF is different from the Well-Architected Framework; CAF is strategic, Well-Architected is technical.
These come up on the exam all the time. Here's how to tell them apart.
AWS Cloud Adoption Framework (CAF)
Focuses on the entire cloud adoption journey (strategy, people, governance, etc.)
Includes business and organizational aspects
Used for planning and assessing readiness before migration
Has six perspectives: Business, People, Governance, Platform, Security, Operations
Phases: Envision, Align, Launch, Scale
AWS Well-Architected Framework
Focuses on designing and operating secure, efficient workloads
Purely technical—no business or people aspects
Used for reviewing existing architectures
Has five pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization
No phases; continuous improvement cycle
Mistake
CAF is a software tool you install.
Correct
CAF is a set of best practices and guidance, not a tool. You can use the AWS Cloud Adoption Readiness Tool (CAR) to assess readiness, but that is a separate free tool.
Mistake
CAF is only for large enterprises.
Correct
CAF is designed for organizations of all sizes. Startups and small businesses can benefit from its structured approach to avoid common pitfalls.
Mistake
CAF is the same as the AWS Well-Architected Framework.
Correct
They are different. CAF covers the entire cloud adoption journey including business and people aspects. Well-Architected focuses on designing technical architectures for existing workloads.
Mistake
The Security perspective is the most important.
Correct
All six perspectives are equally important. Neglecting any one can lead to failure. For example, ignoring the People perspective can cause resistance to change.
Mistake
Once you complete the Scale phase, you stop using CAF.
Correct
CAF is iterative. Organizations should continuously assess and improve their capabilities as they adopt new services or scale.
The six perspectives are Business, People, Governance, Platform, Security, and Operations. Each addresses a specific area of cloud adoption. Business focuses on strategy and finance; People on training and culture; Governance on policies and compliance; Platform on technical architecture; Security on data protection and identity; Operations on monitoring and incident management. For the exam, remember them as B-P-G-P-S-O (Business, People, Governance, Platform, Security, Operations).
CAF is a strategic framework for planning and executing cloud adoption across the entire organization, including business and people aspects. The Well-Architected Framework is a technical framework for designing and reviewing specific workloads. CAF has six perspectives; Well-Architected has five pillars. Use CAF when starting your cloud journey; use Well-Architected for ongoing architecture reviews.
The Envision phase. In this phase, you define business objectives, identify stakeholders, and create a business case that outlines expected benefits, costs, and risks. This phase sets the strategic direction for cloud adoption.
CAF's Security perspective provides guidance on identity and access management, detective controls, infrastructure security, data protection, and incident response. It helps organizations assess their security maturity and implement best practices like least privilege and encryption.
Yes, CAF is free. It is documentation and guidance available on the AWS website. The AWS Cloud Adoption Readiness Tool (CAR) is also free. However, implementing the recommendations may involve costs for AWS services.
The AWS Cloud Adoption Readiness Tool (CAR) is a free online tool that helps organizations assess their readiness across the six CAF perspectives. It generates a report with maturity scores and recommendations for improvement. It is used during the Align phase.
No, CAF is specific to AWS. It is designed by AWS based on their experiences. However, the general principles of having a structured approach to cloud adoption apply to any cloud provider.
You've just covered AWS Cloud Adoption Framework (CAF) — now see how well it sticks with free CLF-C02 practice questions. Full explanations included, no account needed.
Done with this chapter?