Study guide

6.2 AWS Snow Family — Snowball Edge Devices

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.2 AWS Snow Family — Snowball Edge Devices

Key Takeaways Explain This Topic AI

The Snow Family provides ruggedized physical devices for offline data transfer when network bandwidth, time, or cost make online transfer impractical.

As of 2026 the Snow Family is two devices: Snowball Edge Storage Optimized (~210 TB usable NVMe) for bulk transfer, and Snowball Edge Compute Optimized (104 vCPUs, up to 416 GB RAM, optional GPU) for edge compute; AWS Snowball Edge is no longer available to new customers.

AWS retired Snowmobile (the 100 PB truck) in April 2024 and discontinued Snowcone on November 12, 2024 — but the SAA-C03 blueprint still references them, so know what each was for.

Rule of thumb: if an online transfer would take longer than about one week, evaluate Snow Family; for true edge compute with no reliable internet, choose the Compute Optimized device.

All Snow devices use 256-bit encryption with AWS KMS keys, tamper-evident enclosures, and a TPM, and AWS performs secure erasure (NIST media sanitization) after ingest.

Last updated: October 2026

What the Snow Family Is For

Quick Answer: Use Snow Family for offline transfer when shipping a disk beats the wire. The current lineup is Snowball Edge Storage Optimized (bulk transfer, large NVMe capacity) and Snowball Edge Compute Optimized (104 vCPUs, GPU option, edge inference). The retired Snowmobile (100 PB truck) and Snowcone (8–14 TB portable) still appear in SAA-C03 questions, so learn their roles.

The core decision is online versus offline . Online services (DataSync, Direct Connect, S3 Transfer Acceleration) need usable bandwidth; Snow devices physically ship the data, sidestepping the network entirely. The classic exam signal is a stated slow or metered link plus terabytes of data plus a deadline .

Current Snow Family (2026)

Availability: AWS Snowball Edge is no longer available to new customers. AWS points new customers to AWS DataSync for online transfers, AWS Data Transfer Terminal for secure physical transfers, or AWS Partner solutions; for edge computing, AWS Outposts. SAA-C03 questions can still expect Snowball Edge.

  • Device Storage Compute Primary use
  • Snowball Edge Storage Optimized ~210 TB usable NVMe 104 vCPUs, up to 416 GB RAM Large offline data migration

Snowball Edge Compute Optimized 28 TB NVMe 104 vCPUs, up to 416 GB RAM, optional GPU Edge ML inference, video/sensor analysis at remote sites

Retired — but still on the exam

  • Device Capacity Status
  • Snowmobile 100 PB (45-foot truck) Retired April 2024 — newer services made it obsolete
  • Snowcone (HDD/SSD) 8 TB / 14 TB Ordering discontinued November 12, 2024

Why this matters: the SAA-C03 question pool (blueprint frozen August 2022) can still describe an "exabyte data-center evacuation" expecting Snowmobile , or a "small, rugged, two-pound edge device" expecting Snowcone . Answer with the device the question implies; in real architecture today you would use multiple Snowball Edge devices or online transfer instead.

Choosing Online vs. Offline, and Security

Estimate transfer time before recommending a device. A useful rule: at a given link speed, days ≈ (data in bits) / (usable bits per second) / 86,400 . If the result exceeds roughly a week — or the link is needed for production traffic — go offline.

  • Data volume Link speed Approx. online time Recommendation
  • 10 TB 100 Mbps ~9 days One Snowball Edge
  • 100 TB 1 Gbps ~12 days One Snowball Edge Storage Optimized
  • 500 TB 1 Gbps ~60 days Several Snowball Edge devices
  • 1 PB 10 Gbps ~12 days Direct Connect or multiple Snowball Edge
  • 5+ PB metered/poor months Many Snowball Edge (Snowmobile retired)
  • Security model
  • Control Detail
  • Encryption 256-bit, keys managed in AWS KMS; data is never decrypted on the device
  • Tamper resistance Tamper-evident enclosure plus a Trusted Platform Module (TPM)
  • Tracking E-ink shipping label and shipment tracking; chain of custody from dispatch to ingest
  • Erasure After data lands in S3, AWS performs NIST 800-88 secure erasure of the device
  • Edge compute on Snowball Edge

The Compute Optimized device runs EC2-compatible instances from AMIs you preload, AWS Lambda functions via AWS IoT Greengrass, and Amazon EKS Anywhere for Kubernetes — all while disconnected. Typical scenarios: a cargo ship classifying camera feeds, an oil rig running predictive-maintenance models, or a forward military site collecting sensor data, with results synced to AWS when connectivity returns.

Common trap: "Establish a high-bandwidth link to keep syncing 80 TB monthly" is a Direct Connect answer, not Snow Family. Snow is for one-time or periodic bulk moves, while Direct Connect is a persistent dedicated connection. Also remember Direct Connect provisioning takes weeks, so it rarely satisfies a "transfer this in the next few days" deadline.

The Snow ingest workflow, step by step

Understanding the operational flow helps you reason about exam scenarios. First you create a Snow job in the console and AWS ships the device. On arrival you connect it to your local network and use the AWS OpsHub graphical tool (or the Snowball client CLI) to unlock the device with a manifest and unlock code, then copy data onto it; OpsHub also manages EC2 instances and services on the device for edge use. You ship the device back, and AWS ingests the data into the destination S3 bucket. Throughout, data is encrypted with KMS keys you control, and the device is wiped per NIST 800-88 after ingest.

Because the unlock code and manifest are delivered separately, a stolen device cannot be read.

Why Snowmobile and Snowcone disappeared

AWS retired Snowmobile because online options (Direct Connect, DataSync) and stacking many Snowball Edge devices became cheaper and faster than chartering a 45-foot truck, and few customers ever needed a single 100 PB move. Snowcone was discontinued as the portfolio consolidated onto the more capable Snowball Edge platform. The takeaway for design questions today: for petabyte-scale moves, parallelize multiple Snowball Edge Storage Optimized devices or use a dedicated Direct Connect link; do not propose the retired truck in a real-world recommendation even though older SAA-C03 items may still name it as the intended answer.

If a question explicitly says "exabyte-scale data-center evacuation" and lists Snowmobile, that is still the keyed answer for the current exam pool; if it instead lists only modern options, choose multiple Snowball Edge devices.