13 - AWS Storage Extras

AWS Snow Family

awssnowballsnow-familydata-migrationedge-computingsaa-c03

Overview

AWS Snowball is a highly secure, portable device that lets you collect and process data at the edge and migrate data in and out of AWS. For migrations of petabytes of data, Snowball may be a good use case.

There are two Snowball Edge device types, differing in storage:

Device Storage
Snowball Edge Storage Optimized 210 TB
Snowball Edge Compute Optimized 28 TB
AWS update (2025-11)

Snowball Edge has been closed to new customers since 2025-11-07, and new customers cannot order any Snow device. The course presents Snowball as the migration and edge answer. Alternatives are DataSync (online), AWS Data Transfer Terminal (physical) and AWS Outposts (edge). The exam may still use the course figures and device specs. AWS source Blog


Data Migration

Transferring data over a network takes time. Example: 100 TB over a 1 Gbit/s connection takes about 12 days.

Network transfer is a poor fit when you have:

  • limited connectivity or limited bandwidth
  • very high network cost
  • shared bandwidth with other applications
  • an unstable connection
  • a transfer that would take over a week
Exam Pattern

Transfer over the network takes over a week, or the connection is slow, limited, costly or unstable -> use a Snowball device.

Upload directly to S3 is simple but may use all your bandwidth. With Snowball:

  1. You receive a physical Snowball device at your own infrastructure.
  2. You load it with your data.
  3. You ship it back to AWS.
  4. AWS runs an export process that moves the data from the Snowball into, for example, an S3 bucket.

Snowball data migration flow

AWSships Snowball 1. receive Your site2. load your data 3. ship back AWS export process4. data lands in S3 bucket Use it when a network transfer takes over a week. Example: 100 TB over 1 Gbit/s takes about 12 days.
Receive the device, load data, ship it back and AWS exports it into S3.

Edge Computing

Process data while it is created at an edge location, for example a truck on the road, a ship at sea or a mining station underground. These places may have no internet access or limited internet access and compute power.

  • Order a Snowball Edge device and do edge computing on it. The Compute Optimized device is dedicated to this use case.
  • You can run EC2 instances or Lambda functions directly on the device.
  • Use cases: pre-process data, machine learning at the edge, transcode media at the edge.
  • Once data is created and processed, send it back to AWS.
Remember

Snowball is used for data migrations and edge computing.


Hands-On Walkthrough

The demo goes through the ordering process without ordering a device.

  1. Enter a job name (e.g. import job).
  2. Choose the job type:
    • Import into Amazon S3: AWS ships a Snowball to you, you send it back.
    • Export from Amazon S3: data is loaded onto the Snowball and shipped to you.
    • Local compute and storage only: edge computing.
  3. Choose the Snow device: Snowball Edge Storage Optimized (210 TB) or the Compute Optimized device. Many older devices have been discontinued and options may change; two options are enough for the exam.
  4. Choose the pricing option (on-demand per-day pricing), the S3 data transfer and the target buckets.
  5. Security: choose how to encrypt data and a service role. The role has access to S3 and lets AWS create a service-linked role so the Snow device can write to your S3 buckets.
  6. Enter the shipping address and shipping speed (one-day or two-day).
  7. Set notifications for the job status.
  8. Review the job summary.

You receive a Snowball Edge, load your data, and send it back with the included shipping label.


Architecture: Snowball into Glacier

Exam Scenario

Snowball cannot import data directly into Glacier.

Solution:

  1. Snowball imports the data into Amazon S3.
  2. An S3 lifecycle policy transitions the objects into Amazon Glacier.

See S3 Lifecycle Rules.


Snowball into Glacier

Snowballimport job Amazon S3objects land here lifecycle policy Amazon Glacierarchive direct import: not possible Snowball into S3 first, then an S3 lifecycle policy moves objects to Glacier.
Go through S3 and an S3 lifecycle policy because there is no direct import into Glacier.

Questions & Answers

Q1: When should you choose Snowball over a network transfer?

Answer:

When the transfer would take over a week, or there is limited bandwidth, high network cost, shared bandwidth or an unstable connection. Example: 100 TB over 1 Gbit/s takes about 12 days.

Q2: Storage Optimized vs Compute Optimized?

Answer:

Storage Optimized has 210 TB, Compute Optimized has 28 TB and is used for edge computing (EC2, Lambda).

Q3: How do you get Snowball data into Glacier?

Answer:

Import into S3 first, then use an S3 lifecycle policy to transition to Glacier. Snowball cannot import directly into Glacier.

Check yourself

Quiz

Flashcards

Click the card (or focus it), then use ← → to move and Space to flip.