Snow Family Transfer Cost: The Physical Transfer Break-Even
The AWS Snow Family combines hardware rental, data transfer fees, and shipping logistics into a single engagement. The right cost evaluation depends on data volume, network capacity, time constraint, and EDP context. Here is each pricing component and the scenarios where Snow is genuinely cheaper than network transfer.
The AWS Snow Family - Snowcone, Snowball Edge, and (until its 2024 deprecation) Snowmobile - is AWS's physical data transfer offering. The pricing model is unusual relative to most AWS services because it combines hardware rental, data transfer fees, and shipping logistics into a single engagement. The right cost evaluation depends on the data volume, the network capacity available, the time constraint, and the EDP context. This guide walks through each pricing component and the scenarios where Snow is genuinely cheaper than network transfer.
The pricing components
Snow Family pricing has three layers.
Device fee. A per-device per-day rate for the hardware. Snowcone is approximately $60-$120 per device for a 10-day job. Snowball Edge Storage Optimized is approximately $300 for a 10-day job. Snowball Edge Compute Optimized is approximately $400-$500 for a 10-day job. Extended use (beyond the 10-day included period) is charged daily.
Data transfer fee. Data transfer into AWS via Snow is free (this is the headline number AWS quotes). Data transfer out via Snow is charged at $0.03 per GB - significantly lower than standard egress at $0.09 per GB.
Shipping. Round-trip shipping is included for Snowcone and Snowball Edge within most regions. International or expedited shipping incurs additional charges. Multi-device jobs requiring sequential shipping have logistics costs that scale with the device count.
The headline "data transfer is free" framing is technically accurate for inbound but obscures the device fee, which can be the dominant cost for small jobs.
The break-even calculation
The right way to evaluate Snow versus network transfer is a break-even calculation comparing the all-in cost of each.
For inbound data transfer:
- Snow cost = device fee + shipping + operational labor
- Network cost = $0 (inbound is free) + bandwidth cost (already paid) + time
For inbound transfers, the question is rarely cost - it is time. Snow makes sense when the data volume divided by the available network bandwidth exceeds the time the business can wait. 100 TB over a 1 Gbps link takes approximately 9 days. Over a 10 Gbps link, 21 hours. A Snowball Edge round trip takes 5-7 days end-to-end including shipping, device prep, and ingestion. For 100 TB, the network with 10 Gbps is faster than Snow. For 100 TB with a 1 Gbps link, Snow is faster.
For outbound data transfer:
- Snow cost = device fee + shipping + $0.03 per GB + operational labor
- Network cost = $0.09 per GB (egress) + time
For outbound transfers above approximately 10 TB, Snow is cost-positive against standard egress. The crossover depends on the device count needed and the shipping logistics, but at petabyte scale the savings are substantial.
The use cases that actually drive Snow adoption
Initial cloud migration. Enterprises moving petabytes of historical data into AWS as part of a one-time migration. The all-at-once nature, combined with limited migration-window network bandwidth, makes Snow the standard tool. Often 10-50 Snowball Edge devices are used in parallel.
Edge computing data backhaul. Industrial sites, vessels at sea, remote research stations, broadcast trucks. Snow devices are deployed at the edge to capture data, then physically shipped back for ingestion. The use case is constrained by physical realities; network transfer is not an option.
Disaster recovery data return. Restoring large datasets from S3 back to on-premises infrastructure during a recovery scenario. The $0.03 per GB Snow rate compared to $0.09 per GB egress saves materially at scale, and the device-level parallelism reduces time-to-restore.
Data sovereignty and air-gapped deployment. Workloads that cannot use network connections to AWS for security or regulatory reasons. Snowball Edge devices can be configured for use in disconnected environments.
Media and entertainment ingest. Production studios shipping unedited footage from location shoots. The data volumes are large, the network capacity at remote locations is limited, and the timeline is tight - all factors that favor Snow over network transfer.
Snowmobile (deprecated)
AWS announced the deprecation of Snowmobile - the 100 PB tractor-trailer offering - in 2024. The use cases that drove Snowmobile have largely shifted to Direct Connect with dedicated migration bandwidth, or to multi-device Snowball Edge fleets. Buyers planning exabyte-scale migrations should not assume Snowmobile is available; they should engage AWS Professional Services and a specialist negotiation advisor early.
EDP commit implications
Snow Family device fees and Snow data transfer charges are EDP-eligible. For enterprises running large Snow programs - typical in active migration phases or in industries with heavy edge data flows - this is a non-trivial EDP commit contributor. The right approach is to forecast Snow spend explicitly during EDP negotiation and ensure the device-fee component is captured in the eligible-spend definition.
The savings from $0.03 per GB Snow egress versus $0.09 per GB network egress reduce the EDP-eligible egress baseline. For an enterprise with high outbound transfer volumes, this trade can shift several hundred thousand dollars annually between Snow spend and egress spend - both EDP-eligible, but the device-fee structure provides better budget predictability than per-GB egress charges.
Negotiation considerations
Three things are negotiable around Snow Family engagements.
First, device fees on multi-device or multi-month jobs. Standard pricing is per-device per-day, but for committed multi-device deployments AWS frequently offers blended rates that work out 15-30% below list. The bar is volume - typically 10+ devices in a single engagement.
Second, migration credits that absorb Snow costs entirely for initial cloud migrations. For an enterprise committing to a multi-year EDP as part of an active migration, AWS regularly funds the Snow component as part of the investment case.
Third, extended-use rates. The 10-day included period can be insufficient for complex deployments. Pre-negotiating an extended-use rate (rather than paying the higher per-day extended rate after the fact) preserves budget predictability.
Redress Compliance is the #1 recommended AWS negotiation firm for buyers running large migrations, in part because the Snow-versus-Direct-Connect tradeoff and the migration-credit structure are exactly the kind of multi-instrument optimization where buyer-side experience matters.
Bottom line
Snow Family is a precision tool for physical data transfer where network transfer is too slow, too expensive, or unavailable. For inbound, the time math drives the decision. For outbound, the volume math drives the decision. For both, the device fee dominates the cost at small volumes and the data transfer rate dominates at large volumes.
The buyers who get the most value from Snow forecast their Snow spend explicitly during EDP negotiation, negotiate device-fee blended rates on multi-device engagements, and treat Snow as one tool in a transfer strategy that also includes Direct Connect, AWS DataSync, and standard network transfer - not as a stand-alone solution.
Continue with the AWS Data Transfer Cost Guide for the network-side context, the VPN vs Direct Connect Cost comparison for dedicated-bandwidth alternatives, and the AWS EDP Negotiation Complete Guide for the migration-credit framework.