Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/41 ▾
  1. 1.Cloud Concepts: Benefits & Economics0/4
    1. The six advantages of cloud computing
    2. Elasticity, scalability, agility, high availability and global reach
    3. Cloud economics: fixed versus variable cost and total cost of ownership
    4. Licensing, rightsizing and automation
  2. 2.Cloud Concepts: Well-Architected & Migration0/5
    1. The six pillars of the Well-Architected Framework
    2. Pillar trade-offs and the AWS Well-Architected Tool
    3. The AWS Cloud Adoption Framework: outcomes, perspectives and phases
    4. Migration strategies: the 7 Rs
    5. AWS migration services and tools
  3. 3.Security: Shared Responsibility & Compliance0/4
    1. Security of the cloud and security in the cloud
    2. How responsibility shifts with the service you choose
    3. Compliance reports, programs and where data lives
    4. Encryption, keys and audit records
  4. 4.Security: IAM & Access Management0/4
    1. The root user and sign-in credentials
    2. IAM users, user groups and roles
    3. Policies, deny rules and least privilege
    4. Federation, IAM Identity Center, Amazon Cognito and secrets
  5. 5.Security: Services & Resources0/4
    1. Blocking web attacks and DDoS: AWS WAF, AWS Shield and AWS Firewall Manager
    2. Detecting threats, flaws and sensitive data: GuardDuty, Inspector and Macie
    3. Collecting, investigating and advising: Security Hub, Detective and Trusted Advisor
    4. AWS Marketplace and where to find security help
  6. 6.Technology: Deployment & Global Infrastructure0/4
    1. Ways to access AWS: console, CLI, SDKs and APIs
    2. Deployment tools and cloud deployment models
    3. Regions, Availability Zones and high availability
    4. Multiple Regions, data residency and edge services
  7. 7.Technology: Compute & Networking0/4
    1. Amazon EC2 instance types, auto scaling and load balancers
    2. Containers, serverless compute, Lightsail and AWS Batch
    3. Inside a VPC: subnets, gateways, security groups and network ACLs
    4. Route 53 and connecting networks to AWS
  8. 8.Technology: Databases & Storage0/4
    1. Relational databases: Amazon RDS, Aurora and databases on EC2
    2. NoSQL, in-memory and graph databases, plus database migration
    3. Amazon S3 object storage, storage classes and lifecycle policies
    4. Block and file storage, Storage Gateway, AWS Backup and disaster recovery
  9. 9.Technology: AI, Analytics & Other Services0/4
    1. AI and machine learning services: pre-trained services and SageMaker AI
    2. Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
    3. Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
    4. Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
  10. 10.Billing, Pricing & Support0/4
    1. EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
    2. Data transfer costs, consolidated billing and cost allocation tags
    3. Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
    4. AWS Support plans, Trusted Advisor, AWS Health and where to get help
Saved in this browser. Move it to another device →
← Cloud Concepts: Well-Architected & Migration

Chapter 2 · Lesson 4 of 5

Migration strategies: the 7 Rs

1 min read

AWS Prescriptive Guidance lists seven migration strategies. Exam questions describe what happens to one application and ask which strategy it is. Focus on how much the application changes and whether the business still needs it.

StrategyWhat happens
Rehost (lift and shift)Servers move to AWS unchanged
RelocateA whole platform moves in bulk to the cloud version of the same platform
Replatform (lift and reshape)Some optimization, such as a managed database, with no redesign
Refactor (re-architect)Redesign for cloud-native features; the most complex and costly path
Repurchase (drop and shop)Replace with a different product, often SaaS
RetainKeep it where it is for now, for example because of data residency
RetireShut it down because it no longer has business value

Example: a clinic moves its self-managed MySQL database from a rack server to Amazon RDS for MySQL and leaves the application code alone. Adopting a managed service without a redesign makes this replatform, not rehost.

If the clinic instead dropped its licensed scheduling software for a SaaS product from another vendor, that would be repurchase. If it kept a records system on site because of a residency rule and planned to revisit later, that would be retain, not retire, since the system still has business value.

Check yourself

1. To cut database administration work, a company moves its self-managed SQL Server database to Amazon RDS for SQL Server. The core application code stays unchanged and nothing is redesigned. Which migration strategy is this?

2. A company decides to stop running its licensed on-premises customer management system and move its users to a software as a service (SaaS) product from a different vendor. Which migration strategy is this?

Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, AWS Well-Architected Framework, An Overview of the AWS Cloud Adoption Framework

AWS Cloud Practitioner cheat sheet: every key fact on one page →