While preparing for the AWS SAP-C02, many candidates get confused by VMware migration strategies. In the real world, this is fundamentally a decision about migration fidelity vs. operational complexity vs. time-to-migrate. Let’s drill into a simulated scenario.
The Scenario #
GlobalRetail Inc. operates a critical inventory management application on their on-premises VMware vSphere 7.0 cluster across three data centers. The application consists of 12 VMs running customized CentOS 7 builds with proprietary kernel modules, specific network configurations, and tightly coupled storage dependencies.
The infrastructure team has received a mandate to migrate this application to AWS within 90 days to reduce operational overhead and improve disaster recovery capabilities. The CTO has emphasized that software configurations, network settings, and application state must be preserved exactly to avoid costly recertification with their compliance auditors.
The Solutions Architect must recommend an approach that balances migration speed, configuration preservation, and operational simplicity.
Key Requirements #
Migrate VMware-based VMs to Amazon EC2 while:
- Preserving all software installations and configuration settings
- Minimizing manual reconfiguration effort
- Completing migration within the 90-day window
- Maintaining audit compliance (no application code changes)
The Options #
A) Configure AWS DataSync agents in each data center to replicate VM datastores to Amazon FSx for Windows File Server. Mount FSx shares via SMB to serve as the VMware datastore. Use VM Import/Export to migrate the virtual machines to Amazon EC2.
B) Use the VMware vSphere Client to export each application VM as an Open Virtualization Format (OVF) image. Create an Amazon S3 bucket in the target AWS region to store the OVF images. Create and apply an IAM role with VM import permissions. Execute the EC2 import command via AWS CLI to convert OVF images to EC2 instances.
C) Configure AWS Storage Gateway in File Gateway mode, export a CIFS share to the on-premises environment. Create backup copies of the VMs in the CIFS share. Log into the AWS Management Console and create an AMI directly from the backup copy. Launch EC2 instances from the AMI.
D) Create a hybrid activation in AWS Systems Manager for the on-premises environment. Download and install the Systems Manager Agent on each on-premises VM. Register the VMs to Systems Manager as managed instances. Use AWS Backup to create snapshots of the VMs and generate AMIs. Launch EC2 instances from the AMIs.
Correct Answer #
Option B - OVF Export → S3 → VM Import/Export → EC2
Step-by-Step Winning Logic #
This solution represents the canonical AWS migration path for VMware workloads requiring high-fidelity configuration preservation:
1. Purpose-Built Service Alignment
- VM Import/Export is AWS’s designated service for converting virtual machine images to EC2 instances
- Natively supports OVF/OVA formats exported from VMware vSphere
- Preserves guest OS configurations, installed software, network settings, and disk layouts without modification
2. Configuration Fidelity
- OVF export captures complete VM state including:
- Virtual hardware configuration (CPU, memory, network adapters)
- Guest OS settings and kernel parameters
- Installed applications and dependencies
- Network interface configurations
- VM Import/Export translates these directly to EC2 equivalents (ENI configurations, EBS volume mappings, instance metadata)
3. Operational Simplicity
- No intermediate infrastructure required (unlike Options A, C, D)
- S3 serves purely as a staging location (pay only for temporary storage)
- AWS CLI automation enables batch processing of multiple VMs
- Clean migration path: VMware → OVF → S3 → EC2 (three steps)
4. Cost Efficiency For a 12-VM migration with an average 100GB disk per VM:
- S3 storage (30 days): ~$28 (1.2TB × $0.023/GB)
- Data transfer out from on-prem: Variable (ISP-dependent)
- VM Import/Export: No additional charge
- Total migration infrastructure cost: <$100
💎 Professional-Level Analysis #
This section breaks down the scenario from a professional exam perspective, focusing on constraints, trade-offs, and the decision signals used to eliminate incorrect options.
🔐 Expert Deep Dive: Why Options Fail #
This walkthrough explains how the exam expects you to reason through the scenario step by step, highlighting the constraints and trade-offs that invalidate each incorrect option.
Prefer a quick walkthrough before diving deep?
[Video coming soon] This short walkthrough video explains the core scenario, the key trade-off being tested, and why the correct option stands out, so you can follow the deeper analysis with clarity.
🔐 The Traps (Distractor Analysis) #
This section explains why each incorrect option looks reasonable at first glance, and the specific assumptions or constraints that ultimately make it fail.
The difference between the correct answer and the distractors comes down to one decision assumption most candidates overlook.
Why not Option A?
- Architectural mismatch: DataSync + FSx is designed for file migration, not VM migration
- FSx for Windows File Server costs ~$0.13/GB-month (1.2TB = $156/month) plus backup costs
- SMB-mounted datastores don’t integrate with VM Import/Export
- Adds unnecessary complexity: DataSync agents → FSx → (undefined VM conversion step)
- Cost impact: $300-600 in unnecessary infrastructure for 90-day window
Why not Option C?
- Fundamental technical flaw: Storage Gateway File Gateway does not support AMI creation from backup files
- CIFS shares store files, not VM images with bootable metadata
- AWS Console cannot “create an AMI from a backup copy” in a file share—this pathway doesn’t exist
- Storage Gateway costs ~$125/month (beyond migration window needs)
- This option describes a non-functional workflow
Why not Option D?
- Service misalignment: Systems Manager + AWS Backup is designed for AWS-native resource management, not VM migration
- Systems Manager Agent on on-prem VMs enables management but does not migrate the VM itself
- AWS Backup cannot snapshot on-premises VMware VMs directly (only supports AWS resources or VMware via AWS Connector for vSphere, not mentioned here)
- Hybrid activation costs: $0.00695/hour per managed instance (~$60/month for 12 VMs)
- This workflow is technically incomplete as described
🔐 The Solution Blueprint #
This blueprint visualizes the expected solution, showing how services interact and which architectural pattern the exam is testing.
Seeing the full solution end to end often makes the trade-offs—and the failure points of simpler options—immediately clear.
graph TB
subgraph "On-Premises Data Center"
VM[VMware vSphere VMs
CentOS 7 + Custom Configs]
vClient[vSphere Client]
end
subgraph "AWS Cloud"
S3[Amazon S3 Bucket
OVF Image Storage]
IAM[IAM Role
vmimport permissions]
CLI[AWS CLI
ec2 import-image]
EC2[EC2 Instances
Migrated VMs]
end
VM -->|1. Export as OVF| vClient
vClient -->|2. Upload OVF images| S3
IAM -.->|3. Authorize| CLI
S3 -->|4. Import source| CLI
CLI -->|5. VM Import/Export| EC2
style VM fill:#FF9900,stroke:#232F3E,color:#fff
style EC2 fill:#FF9900,stroke:#232F3E,color:#fff
style S3 fill:#569A31,stroke:#232F3E,color:#fff
style CLI fill:#3B48CC,stroke:#232F3E,color:#fff
Diagram Note: The workflow shows the direct three-step migration path: OVF export from VMware → S3 staging → VM Import/Export conversion to EC2, with IAM providing the necessary service permissions.
🔐 The Decision Matrix #
This matrix compares all options across cost, complexity, and operational impact, making the trade-offs explicit and the correct choice logically defensible.
At the professional level, the exam expects you to justify your choice by explicitly comparing cost, complexity, and operational impact.
| Option | Est. Complexity | Est. Migration Cost | Migration Duration | Pros | Cons |
|---|---|---|---|---|---|
| A - DataSync + FSx | High | $400-700 (FSx $156/mo × 3 months + DataSync agent setup) | 4-6 weeks | Automated replication; Good for ongoing file sync | Architectural mismatch; FSx unnecessary post-migration; Doesn’t integrate with VM Import |
| B - OVF + VM Import ✅ | Medium | $50-150 (S3 storage + data transfer) | 2-3 weeks | Purpose-built for VM migration; Config preservation guaranteed; Clean workflow | Requires manual OVF export per VM; Bandwidth-dependent upload time |
| C - Storage Gateway + CIFS | Medium | $300-500 (Gateway appliance + S3 backend × 3 months) | Not achievable | Low on-prem infrastructure changes | Technically non-functional: Cannot create AMI from CIFS file backups |
| D - Systems Manager + Backup | High | $200-400 (Hybrid activation $60/mo × 3 + agent deployment) | Not achievable | Good for post-migration management | Incomplete workflow: AWS Backup doesn’t snapshot on-prem VMware VMs as described |
Key Financial Insight: Option B delivers a 75-85% cost reduction compared to alternatives while being the only technically complete solution. The cost delta ($350-650 saved) represents wasted spend on services that provide no migration value.
🔐 Real-World Practitioner Insight #
This section connects the exam scenario to real production environments, highlighting how similar decisions are made—and often misjudged—in practice.
This is the kind of decision that frequently looks correct on paper, but creates long-term friction once deployed in production.
Exam Rule #
For the SAP-C02 exam, when you see:
- “VMware migration” + “preserve configurations/settings”
- “On-premises VMs” → “EC2”
- Need for exact software/config fidelity
Always select VM Import/Export with OVF/OVA format as the primary mechanism.
Memorize this decision tree:
- VMware → AWS with config preservation = VM Import/Export
- Physical servers → AWS = AWS Application Migration Service (MGN)
- Database migration = AWS DMS
- File shares = DataSync + FSx/EFS
Real World #
In production environments with large-scale VMware migrations (50+ VMs), we typically use:
AWS Application Migration Service (MGN) for most workloads:
- Continuous block-level replication (minimal downtime)
- Automated cutover orchestration
- Better suited for large fleets
- Cost: ~$0.07/hour per replicating server
VM Import/Export remains optimal for:
- Small migrations (<20 VMs)
- Highly customized VMs with exotic configurations
- Compliance scenarios requiring “lift-and-shift” with zero modification
- Air-gapped migrations (sneakernet via physical drives to S3)
Additional real-world considerations not in the exam:
- Network bandwidth planning: 100GB VM = 2-10 hours upload on 100Mbps connection
- Licensing: Windows VMs require License Mobility verification before migration
- Post-migration right-sizing: Initial imports use source VM sizing; immediate cost optimization opportunity
- Hybrid period: Often run parallel on-prem/AWS for 30-60 days during validation
Cost reality check: For GlobalRetail’s 12-VM scenario:
- Exam answer (Option B): ~$100 migration cost
- Real-world with MGN: ~$350 (12 VMs × 2 weeks × $0.07/hr × 24hr × 7 days = $282 + validation period)
- Real-world with VMware Cloud on AWS: $8,000-12,000/month (overkill for this use case)
The exam tests your knowledge of AWS-native migration services; production adds layers of validation, rollback planning, and hybrid operation that exam scenarios abstract away.