Moving to AWS is an organizational change as much as a technical one. The AWS Cloud Adoption Framework structures that change, the 7 Rs classify how each application moves, and migration services do the moving.
AWS Cloud Adoption Framework
The AWS Cloud Adoption Framework (AWS CAF) is AWS guidance for the organizational side of moving to the cloud. It helps find and prioritize opportunities, check how ready the organization is, and plan the transformation in steps.
How it works
- AWS CAF ties cloud adoption to business outcomes: less business risk, better ESG performance, more revenue and more operational efficiency.
- Its capabilities sit in six perspectives, each owned by a group of stakeholders.
- The journey repeats four phases: Envision, Align, Launch and Scale.
| Perspective | Focus |
|---|---|
| Business | Cloud investments that serve business outcomes |
| People | Culture, structure, leadership, workforce |
| Governance | Orchestrating initiatives, managing risk |
| Platform | Scalable hybrid platform, modernization, cloud-native builds |
| Security | Confidentiality, integrity and availability of data and workloads |
| Operations | Services delivered at the level the business agreed |
Business, People and Governance are the business side; Platform, Security and Operations are the technical side.
Exam cues
- If the question says culture, training or organizational structure, think People perspective.
- If the question says risk and benefits of cloud initiatives, think Governance perspective.
- If the question says pilots in production, think Launch phase; finding gaps, think Align.
Remember
- Six perspectives: Business, People, Governance, Platform, Security, Operations.
- Four phases: Envision, Align, Launch, Scale.
- Outcomes: reduced business risk; improved ESG performance; increased revenue; increased operational efficiency.
- Business perspective: 8 capabilities, executive stakeholders. Platform: 7, CTO and engineers. Operations: 9, including patch and incident management.
Trap: AWS CAF has six perspectives and the Well-Architected Framework has six pillars. Security appears in both; questions about workforce or governance point to CAF, questions about workload design point to Well-Architected.
From the AWS docs (18)
- The AWS Cloud Adoption Framework (AWS CAF) uses AWS experience and best practices to help organizations digitally transform and accelerate business outcomes through innovative use of AWS.
- AWS CAF helps identify and prioritize transformation opportunities, evaluate and improve cloud readiness, and iteratively evolve a transformation roadmap.
- Key business outcomes of cloud transformation in AWS CAF include reduced business risk, improved environmental, social and governance (ESG) performance, and increased revenue and operational efficiency.
- AWS CAF describes four transformation domains in a value chain: technological transformation enables process transformation, which enables organizational transformation, which enables product transformation.
- AWS CAF groups its foundational capabilities in six perspectives: Business, People, Governance, Platform, Security and Operations.
- The Business perspective helps ensure cloud investments accelerate digital transformation and business outcomes; common stakeholders include the CEO, CFO, COO, CIO and CTO.
- The People perspective bridges technology and business, focusing on culture, organizational structure, leadership and workforce.
- The Governance perspective helps orchestrate cloud initiatives while maximizing organizational benefits and minimizing transformation-related risks.
- The Platform perspective helps build an enterprise-grade, scalable hybrid cloud platform, modernize existing workloads and implement new cloud-native solutions.
- The Security perspective helps achieve the confidentiality, integrity and availability of data and cloud workloads.
- The Operations perspective focuses on delivering cloud services at a level agreed with business stakeholders.
- AWS CAF recommends four iterative and incremental phases: Envision, Align, Launch and Scale.
- Envision shows how cloud accelerates business outcomes; Align finds capability gaps across the six perspectives; Launch delivers pilots in production; Scale expands pilots to the desired scale.
- The CAF Platform perspective has seven capabilities, and its common stakeholders are the CTO, technology leaders, architects and engineers.
- The CAF Operations perspective has nine capabilities: observability, event management (AIOps), incident and problem management, change and release management, performance and capacity management, configuration management, patch management, availability and continuity management, and application management.
- The CAF Business perspective has eight capabilities: strategy management, portfolio management, innovation management, product management, strategic partnership, data monetization, business insights and data science. Its common stakeholders are the CEO, CFO, COO, CIO and CTO.
- The CAF Security perspective has nine capabilities: security governance, security assurance, identity and access management, threat detection, vulnerability management, infrastructure protection, data protection, application security and incident response.
- The CAF Governance perspective has seven capabilities: program and project management, benefits management, risk management, cloud financial management, application portfolio management, data governance and data curation.
The 7 Rs of migration
A migration strategy is how one workload moves to AWS. AWS names seven, the 7 Rs, for choosing how to move or handle a workload.
How it works
- Assess each application: its business value, dependencies, risk and target.
- Pick one of the 7 Rs for it.
- For a large migration, consider rehosting, relocating or replatforming first, then modernizing afterward.
| Strategy | Also called | What happens |
|---|---|---|
| Rehost | Lift and shift | Move unchanged |
| Replatform | Lift, tinker and shift | Move with some optimization, such as a managed database |
Exam cues
- If the question says move an application without changes, think rehost.
- If the question says move a SQL Server database to Amazon RDS for SQL Server, think replatform, because the move adds an optimization.
- If the question says modernize during a large migration, consider rehost, relocate or replatform first, because refactoring is the most complex and costly strategy.
Remember
- Seven strategies: retire, retain, rehost, relocate, repurchase, replatform, refactor.
- Refactor is the most complex and costly.
- For a large migration, rehost, relocate or replatform first; modernization can follow.
Trap: Rehosting moves an application without changes. Replatforming adds some optimization during the move.
From the AWS docs (4)
- The seven migration strategies, the 7 Rs, are retire, retain, rehost, relocate, repurchase, replatform, and refactor or re-architect.
- Rehost, also called lift and shift, moves an application to AWS without changing it.
- Replatform, also called lift, tinker and shift, moves an application and adds some optimization, such as moving a SQL Server database to Amazon RDS for SQL Server.
- Refactoring is the most complex and costly migration strategy; for large migrations AWS recommends rehosting, relocating or replatforming first and modernizing afterward.
Migration services
AWS migration services help discover on-premises servers, move them to AWS and track migration progress. Some were renamed or closed to new customers, so exam questions may use older names.
How it works
- Discovery: AWS Application Discovery Service collects server configuration, usage and network connections, so servers can be grouped into applications.
- Move servers: AWS Application Migration Service replicates servers continuously and launches them on AWS with short cutovers.
- Track: AWS Migration Hub shows each application’s migration status across tools, including AWS Application Migration Service and AWS Database Migration Service (AWS DMS).
| Service | Stage | Status (November 2026) |
|---|---|---|
| AWS Application Discovery Service | Discover | Closed to new customers since November 7, 2025 |
| AWS Application Migration Service | Move servers (rehost) | Now named AWS Transform MGN |
| AWS Migration Hub | Track | Tracks application migration across tools |
AWS Transform provides similar capabilities to Application Discovery Service.
Exam cues
- If the question says lift and shift servers with minimal downtime, think AWS Application Migration Service.
- If the question says discover on-premises servers and their dependencies, think AWS Application Discovery Service.
- If the question says track migration progress in one place, think AWS Migration Hub.
Remember
- Application Migration Service cutovers typically take minutes.
- Application Discovery Service stopped accepting new customers on November 7, 2025.
Trap: AWS DMS moves databases, not servers. A question about migrating whole servers points to AWS Application Migration Service.
From the AWS docs (9)
- AWS Application Migration Service, now named AWS Transform MGN, automates migrating physical, virtual and cloud servers to AWS with minimal downtime, typically with cutover windows of minutes.
- AWS Transform MGN continuously replicates source servers at the block level and converts them to launch on AWS.
- AWS Application Migration Service is the primary service AWS recommends for lift-and-shift migrations.
- AWS Application Discovery Service plans migrations by collecting usage and configuration data about on-premises servers and databases, including network connections between servers.
- AWS Application Discovery Service closed to new customers on November 7, 2025; AWS Transform provides similar capabilities.
- AWS Migration Hub provides a single place to discover servers, plan migrations and track the status of each application migration, whichever migration tool is used.
- AWS Migration Hub receives migration status updates from AWS Application Migration Service and AWS Database Migration Service.
- Application Discovery Service Agentless Collector is an OVA appliance deployed in VMware vCenter that reports VM performance and utilization without per-VM agents, but cannot see processes or network connections; the Discovery Agent, installed on each server, collects those too.
- VM Import/Export can export most EC2 instances as VMs for Citrix Xen, Microsoft Hyper-V or VMware vSphere, storing the image in S3; instances with Windows, SQL Server or AWS Marketplace software cannot be exported.
Migration strategy choices
Migration strategies describe what to do with an application when moving to the cloud. The choice can be to replace it, redesign it, move it to a cloud version of its platform, keep it where it is, or retire it.
How it works
- Consider whether the application has business value. If it does not, retire it by decommissioning or archiving it. If it needs to stay in its source environment, retain it. Retire, retain
- To replace it with a different product or version, choose repurchase. For example, a traditionally licensed application can be replaced by software as a service (SaaS).
- To move servers to a cloud version of the same platform without rewriting applications or changing operations, choose relocate.
- To change the application’s architecture to use cloud-native features, choose refactor.
| Strategy | What happens |
|---|---|
| Retire | Decommission or archive an application with no business value |
| Retain | Keep an application in the source environment |
| Repurchase | Replace an application with another product or version |
| Relocate | Move servers to a cloud version of the same platform |
| Refactor | Change the architecture to use cloud-native features |
Exam cues
- If the question says replace an on-premises application with SaaS, think repurchase, because a different product takes its place.
- If the question says redesign an application for scalability, think refactor, because its architecture changes to use cloud-native features.
- If the question says an application has no business value, think retire, because decommissioning or archiving it removes maintenance and hosting costs.
- If the question says an application depends on specialized hardware, think retain, because it can remain in the source environment.
- If the question says move servers to a cloud version of the same platform without changing operations, think relocate, because it preserves the existing operations.
Remember
- Repurchase is also called drop and shop; refactor is also called re-architect.
- Refactor is the most complex and costly strategy. For large migrations, AWS recommends rehosting, relocating or replatforming first, then modernizing.
Trap: Retire and retain are different choices. Retire decommissions or archives an application with no business value; retain keeps it in the source environment.
From the AWS docs (6)
- Repurchase, also called drop and shop, replaces an application with a different version or product, such as moving from a traditional license to software as a service (SaaS).
- Refactor or re-architect modifies the application's architecture to use cloud-native features for agility, performance and scalability.
- Refactoring is the most complex and costly migration strategy; for large migrations AWS recommends rehosting, relocating or replatforming first and modernizing afterward.
- Retire decommissions or archives an application that has no business value to keep or move, which removes its maintenance and hosting cost.
- Retain keeps an application in the source environment, for example for data residency, high risk, unresolved dependencies, recent upgrades or specialized hardware.
- Relocate moves many servers at once from an on-premises platform to a cloud version of that platform without new hardware, rewrites or operational changes, and can also move resources to another VPC, Region or account.
Migration planning and tracking
Migration planning tools help a company build a business case for AWS and follow application migrations. Migration Evaluator supports the business case, while AWS Migration Hub provides one place to plan and track migrations.
How it works
- Build the case: Migration Evaluator finds over-provisioned on-premises instances and compares bring your own license (BYOL) with License Included options.
- Plan and track: Migration Hub discovers servers, helps plan migrations and shows each application’s migration status across tools. It receives updates from AWS Application Migration Service and AWS Database Migration Service.
Exam cues
- If the question asks for a data-driven business case for AWS, think Migration Evaluator, because it identifies over-provisioned instances and compares licensing options.
- If the question asks for one place to track application migrations across tools, think AWS Migration Hub, because it receives migration status updates from other services.
Remember
- Migration Hub closed to new customers on November 7, 2025. AWS Transform offers similar capabilities.
Trap: Migration Hub tracks migration status across tools; Migration Evaluator builds the business case. Choose the tool that fits the question.
From the AWS docs (4)
- AWS Migration Hub provides a single place to discover servers, plan migrations and track the status of each application migration, whichever migration tool is used.
- AWS Migration Hub closed to new customers on November 7, 2025; AWS Transform offers similar capabilities.
- AWS Migration Hub receives migration status updates from AWS Application Migration Service and AWS Database Migration Service.
- Migration Evaluator builds a data-driven business case for AWS, discovers over-provisioned on-premises instances and compares BYOL with License Included options.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 31 cards as a list
What are the six perspectives of the AWS Cloud Adoption Framework (AWS CAF)?
Business, People, Governance, Platform, Security and Operations.
Which AWS Cloud Adoption Framework perspective focuses on culture, organizational structure, leadership and workforce?
The People perspective.
Which AWS Cloud Adoption Framework perspective focuses on minimizing transformation risks while maximizing organizational benefits?
The Governance perspective.
Which AWS Cloud Adoption Framework perspective covers building a scalable hybrid cloud platform and modernizing workloads?
The Platform perspective.
Which business outcomes does the AWS Cloud Adoption Framework name for cloud transformation?
Reduced business risk, improved ESG performance, and increased revenue and operational efficiency.
What are the four phases of the AWS Cloud Adoption Framework transformation journey, in order?
Envision, Align, Launch, Scale.
In the AWS Cloud Adoption Framework journey, in which phase does a company find capability gaps and stakeholder concerns?
Align.
Which AWS Cloud Adoption Framework perspective has the CFO and CEO among its common stakeholders and makes sure cloud investments serve business outcomes?
The Business perspective.
Is the AWS Cloud Adoption Framework a migration tool that moves servers to AWS?
No. It is guidance for planning and running the organizational change; migration services such as AWS Application Migration Service move the servers.
In the AWS Cloud Adoption Framework (AWS CAF), which perspective has the CTO, architects and engineers as its common stakeholders?
The Platform perspective.
It covers the cloud environment and workload delivery.
Which AWS CAF perspective includes patch management, incident and problem management, and observability?
The Operations perspective.
Its nine capabilities keep cloud services running at the level agreed with the business.
Which AWS CAF perspective includes portfolio management, data monetization and strategic partnership?
The Business perspective.
Its stakeholders are executives such as the CEO, CFO and CIO.
Which CAF Security capability is about protecting workloads against unintended and unauthorized access and potential vulnerabilities?
Infrastructure protection. The Security perspective has nine capabilities, including threat detection, vulnerability management, data protection and incident response.
Data governance and data curation belong to which CAF perspective?
Governance, along with program and project management, benefits management, risk management, cloud financial management and application portfolio management.
What are the 7 Rs of migration to AWS?
Retire, retain, rehost, relocate, repurchase, replatform, and refactor (re-architect).
A company moves its servers to Amazon EC2 exactly as they are, with no code changes. Which migration strategy is this?
Rehost (lift and shift).
A company moves its self-managed SQL Server database to Amazon RDS for SQL Server during migration. Which migration strategy is this?
Replatform (lift, tinker and shift). It adds an optimization, a managed database, without rewriting the application.
For a large migration, should a company refactor every application while moving it to AWS?
No. Refactor is the most complex and costly strategy. AWS recommends rehost, relocate or replatform first, then modernize after the migration.
Which AWS service rehosts physical, virtual and cloud servers on AWS with continuous block-level replication and short cutovers?
AWS Application Migration Service, now named AWS Transform MGN.
Which AWS service collected configuration, usage and network connection data about on-premises servers to plan a migration?
AWS Application Discovery Service. It closed to new customers on November 7, 2025; AWS Transform offers similar capabilities.
Which AWS service does AWS recommend first for a lift-and-shift migration of servers?
AWS Application Migration Service (AWS Transform MGN).
Does AWS Migration Hub itself copy servers to AWS?
No. It discovers, plans and tracks migrations; tools such as AWS Application Migration Service and AWS DMS do the moving.
A company moves its databases with AWS Database Migration Service and its servers with AWS Application Migration Service. Where can it follow the status of both?
In AWS Migration Hub, which receives migration status updates from both services.
A company replaces its on-premises CRM with a SaaS CRM product. Which migration strategy is this?
Repurchase (drop and shop).
A company rebuilds a monolith as microservices on AWS to scale and release features faster. Which migration strategy is this?
Refactor (re-architect). It is the most complex and costly strategy.
During a migration assessment, a company finds an application nobody uses. Which migration strategy applies?
Retire. Decommissioning it removes its maintenance and hosting costs.
An application depends on factory hardware that has no cloud equivalent. Which migration strategy fits for now?
Retain. Keep it in the source environment until it can be migrated.
A company moves hundreds of VMware VMs to a cloud version of VMware without buying hardware or changing operations. Which migration strategy is this?
Relocate. It moves servers to a cloud version of the same platform.
Which AWS service gives one place to track the migration status of each application across migration tools?
AWS Migration Hub. It closed to new customers on November 7, 2025; AWS Transform offers similar capabilities.
A company needs a business case comparing its current on-premises costs with AWS before deciding to migrate. Which AWS offering helps?
Migration Evaluator. It finds over-provisioned servers and compares license options.
How can Migration Evaluator help a company prepare for a move to AWS?
It builds a data-driven business case and identifies over-provisioned on-premises instances.