Skip to content
BytePatterns

Moving Data Into AWS

AWS for Interviews: lesson 17 of 18

Divide terabytes by your real bandwidth before you choose a tool.

Lesson 17 of 18 · 6 min

Moving Data Into AWS

Step 1 of 11

50 TB on a file server, one 1 Gbps link to AWS. Before picking a tool, work out how long the network takes.

The Idea

First do the arithmetic: days = TB × 8×10¹² ÷ (link bits per second × usable share) ÷ 86,400. Online, DataSync copies NFS, SMB, HDFS or object storage into S3, EFS or FSx, encrypting and verifying the data. Transfer Family gives partners SFTP, FTPS, FTP or AS2 endpoints in front of S3 or EFS. S3 Transfer Acceleration brings distant uploads in through edge locations. When the network is too slow, data travels on devices.

Real-World Example

50 TB over a 1 Gbps link at 80% takes 5.8 days, so DataSync is fine. 100 TB takes 11.6 days; copying it onto a 210 TB Snowball Edge over the 10 Gbps LAN takes 1.2 days before shipping.

The Tradeoff

Snowball Edge is closed to new customers (as of October 2026); they use DataSync, or bring drives to an AWS Data Transfer Terminal. Online copies share the link with production, so throttle them.

Hands-On

# how many days does the network need?
tb, gbps, usable = 50, 1, 0.8
seconds = tb * 8e12 / (gbps * 1e9 * usable)
print(round(seconds / 86400, 1))  # 5.8

Your turn

Fill in the blank.

tb, gbps, usable = 100, 1, 0.8
seconds = tb * 8e12 / (gbps * 1e9 * usable)
print(round(seconds / ___, 1))  # days

Mini quiz

1 / 3

About how long does 50 TB take over a 1 Gbps link you can use at 80%?

Sources

Keep going

Certification prepPreparing for DEA-C01? Try the free 65-question practice exam

ReferenceBig-O cheat sheetPatterns cheat sheet

New lessons land every few weeks

Leave an address and we will tell you when the next one is up. That is the only reason we will use it.

One address, stored so we can email you. Nothing else, ever.