HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Migration Architecture in Cloud Computing

Learn about Migration Architecture in this comprehensive Cloud Computing tutorial. Offline vs Online.

⚡ Total XP: 0|💻 cloud XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

🚀 LEVEL UP TO SENIOR:Unlock 500+ Advanced Practical Challenges & Exercises.

🎓 COURSERA PARTNER:Earn professional Google, Meta, and IBM certificates to supercharge your resume.

1Offline Migration

The Snow family bypasses the internet entirely. It is highly secure, using 256-bit encryption and tamper-evident enclosures. It is the only feasible way to migrate dozens of petabytes of legacy data within a strict timeline.

2Step-by-Step Breakdown

Hybrid Storage. Many companies cannot move 100% to the cloud immediately. AWS offers tools to bridge on-premises servers with AWS storage.

AWS Storage Gateway. A virtual appliance installed in your on-premises data center that seamlessly connects local apps to AWS storage.

File Gateway. Provides local servers with an NFS/SMB mount, but actually stores the files as objects in an S3 bucket.

Volume Gateway. Provides block storage (iSCSI) to local servers while backing up point-in-time snapshots to AWS EBS.

Knowledge Check. Which Storage Gateway type allows your local on-premises Windows servers to mount an SMB shared drive that is actually backed by Amazon S3?

→Volume Gateway
→File Gateway

The Bandwidth Problem. Moving Petabytes (PB) of data over a 1Gbps internet connection would take years. AWS created physical devices to solve this.

AWS Snowcone. A small, rugged, secure device for edge computing and moving up to 8 TB of data.

AWS Snowball Edge. A heavy suitcase-sized device that AWS ships to your data center. You load it up, ship it back, and AWS plugs it into S3.

AWS Snowmobile. An actual 45-foot long shipping container pulled by a semi-truck, used for Exabyte-scale data migration.

Summary. Use Storage Gateway for hybrid operations, and the Snow family for massive offline migrations.

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Trying to migrate a very large on-premises dataset over the internet instead of using Snow Family

// Rule of thumb: if (dataSizeInTB / bandwidthInTBperDay) > ~1 week, consider Snowball

The Solution //

Transferring tens or hundreds of terabytes over a standard internet link can take weeks and saturate the network. Once the math on transfer time (data size / available bandwidth) exceeds about a week, physical transfer via AWS Snowball becomes faster and often cheaper than network transfer.

The Error //

Deploying Storage Gateway without matching the right gateway type to the actual access pattern

// File-based NFS/SMB access -> File Gateway
// Block storage volumes -> Volume Gateway
// Backup software expecting tape -> Tape Gateway

The Solution //

Storage Gateway has distinct types (File Gateway, Volume Gateway, Tape Gateway) for different use cases — using a Volume Gateway when the application actually needs file-based NFS/SMB access (or vice versa) causes integration friction. Match the gateway type to how the on-prem application actually reads and writes data.