Study guide

6.1 The 7 Rs of Cloud Migration

AWS Solutions Architect Associate SAA-C03

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework

2 Domain 1: Design Secure Architectures (30%)

1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services

3 Domain 2: Design Resilient Architectures (26%)

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration

4 Domain 3: Design High-Performing Architectures (24%)

3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR

5 Domain 4: Design Cost-Optimized Architectures (20%)

4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools

6 VPC and Networking Deep Dive

5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services

7 Migration, Transfer, and Hybrid Services

6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family

8 Serverless Architecture and Application Services

7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR

9 Advanced Topics and Exam Scenarios

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together

6.1 The 7 Rs of Cloud Migration

Key Takeaways Explain This Topic AI

The 7 Rs are migration strategies: Retire, Retain, Relocate, Rehost (lift-and-shift), Replatform (lift-tinker-and-shift), Repurchase (drop-and-shop), and Refactor (re-architect).

Rehost (lift-and-shift) is the fastest migration approach — move applications as-is to EC2 without code changes; AWS Application Migration Service (MGN) automates it with continuous block-level replication.

Replatform makes minor optimizations during migration (for example, self-managed MySQL to Amazon RDS) without rewriting the application code.

Refactor / re-architect offers the most long-term benefit by redesigning applications cloud-native (serverless, microservices) but takes the most time and money.

Heterogeneous database migrations (Oracle to Aurora PostgreSQL) need AWS Schema Conversion Tool (SCT) first, then AWS Database Migration Service (DMS); homogeneous migrations need DMS only.

Last updated: June 2026

The 7 Migration Strategies

Quick Answer: The 7 Rs order migration strategies from simplest to most transformative: Retire (decommission), Retain (keep on-premises), Relocate (move VMware to VMware Cloud on AWS), Rehost (lift-and-shift to EC2), Replatform (move with minor tuning), Repurchase (switch to SaaS), and Refactor (re-architect cloud-native). On the SAA-C03 exam, the keywords "as-is," "fastest," and "minimal changes" almost always point to Rehost .

A migration assessment ranks each application against effort versus benefit. The exam frequently gives a scenario sentence and expects you to map it to exactly one R, so memorize the trigger phrase for each row below.

  • Strategy What you do Effort Cloud benefit Worked example
  • Retire Decommission apps nobody uses Lowest Cost reduction Legacy reporting tool with zero logins for a year
  • Retain Keep on-premises for now Low Deferred App pending a vendor licensing decision
  • Relocate Move VMware vSphere stack to VMware Cloud on AWS Low Same tooling 100 VMs you cannot re-IP yet

Rehost Lift-and-shift to EC2, no code change Low-Med Quick exit from data center Web tier moved straight to EC2 via MGN

Replatform Lift-tinker-and-shift Medium Some managed benefits Self-managed MySQL to RDS; Tomcat app to Elastic Beanstalk

Repurchase Drop-and-shop to SaaS Medium No more ops On-prem CRM to Salesforce; mail to Microsoft 365

Refactor Re-architect cloud-native Highest Maximum (scale, agility) Monolith broken into Lambda + API Gateway microservices

Mapping scenarios to a strategy

"Migrate 500 servers as fast as possible" → Rehost (MGN).

"Reduce database admin work without changing the app" → Replatform to RDS/Aurora.

"We want event-driven serverless" → Refactor .

"This app has no remaining users" → Retire .

"Too entangled to move this quarter" → Retain .

Common trap: candidates pick Refactor because it sounds best. Refactor maximizes long-term benefit but is the slowest and costliest; when the scenario stresses speed, deadline, or "no code changes," Rehost wins.

AWS Migration Services and Tooling

AWS Migration Hub is the single pane of glass that tracks application status across the underlying tools — it does not move data itself. The execution services are summarized below.

  • Service Purpose Exam trigger
  • Migration Hub Central progress tracking, app grouping "Single dashboard for all migrations"

Application Migration Service (MGN) Automated rehost of servers to EC2 "Lift-and-shift servers with minimal downtime"

Database Migration Service (DMS) Move databases, optional ongoing replication "Migrate a database, keep the source running"

Schema Conversion Tool (SCT) Convert schema between different engines "Oracle to PostgreSQL" / "SQL Server to MySQL"

  • DataSync Online file/object transfer to S3/EFS/FSx "Bulk file migration over the network"
  • Snow Family Offline physical transfer "Limited bandwidth, terabytes of data"
  • Application Migration Service (MGN) — the rehost engine

MGN installs a lightweight agent on each source server and performs continuous, block-level replication into a low-cost staging area in your AWS account. Because replication is continuous, the final cutover window is minutes, not hours. You can launch test instances from the replicated data without touching production, validate, then perform a non-disruptive cutover. MGN supports physical, virtual (VMware/Hyper-V), and other-cloud servers, all targeting EC2.

Database Migration Service (DMS) and Schema Conversion Tool (SCT)

DMS keeps the source database fully operational during migration and supports change data capture (CDC) for ongoing replication, enabling near-zero-downtime cutovers.

Homogeneous (MySQL→RDS MySQL, Oracle→Oracle): same engine, DMS only — no schema conversion required.

Heterogeneous (Oracle→Aurora PostgreSQL, SQL Server→MySQL): different engine, run SCT first to convert tables, views, and stored procedures, then DMS to move and replicate the data.

Worked example: Migrate a 2 TB Oracle database to Aurora PostgreSQL with under five minutes of downtime. Convert the schema with SCT, start a DMS task with full-load + CDC, let CDC catch the change backlog, then cut the application over to the Aurora endpoint.

How the strategies sequence in a real program

Large migrations rarely use a single R; an enterprise portfolio typically blends several. A practical sequence is: first Retire the dead weight so you never pay to move it, then Rehost the bulk of servers quickly with MGN to vacate the data center and stop the lease, and finally Refactor the few high-value applications where cloud-native rewrites pay off. This "move fast, optimize later" pattern is why the exam treats Rehost as the default mass-migration answer and Refactor as a targeted, post-migration investment rather than a day-one choice.

Trap to watch: AWS Migration Hub does not move anything. If a question asks which service transfers the workload, it is MGN, DMS, DataSync, or Snow — Migration Hub only aggregates status and discovery data across those tools. Likewise, Relocate is narrow: it specifically means moving a VMware vSphere environment to VMware Cloud on AWS without converting the VMs to native EC2, so reserve it for scenarios that explicitly mention VMware and the desire to keep existing vSphere operations.

When in doubt between Rehost and Replatform, decide on whether any change is made: zero changes is Rehost; swapping a self-managed component for a managed equivalent (a database to RDS, a runtime to Elastic Beanstalk) is Replatform.