A company must migrate 10 PB of data to Amazon S3 within 6 weeks. The data center has a 500 Mbps internet uplink; other applications share the link. The company can use 80% of the internet bandwidth for this one-time migration. Which solution meets these requirements?

The correct solution is to use multiple AWS Snowball devices. Given 10 PB of data and a 6-week (42-day) deadline, the available internet bandwidth (80% of 500 Mbps = 400 Mbps) is insufficient. 400 Mbps allows for approximately 43.2 TB of data transfer over 42 days (400 Mbps 60 seconds/minute 60 minutes/hour 24 hours/day 42 days / 8 bits/byte / 1024^4 TB/byte ≈ 1.55 TB). This is far less than 10 PB. AWS Snowball devices are designed for large-scale data migrations where network bandwidth is a bottleneck, offering physical shipment to AWS for direct import into S3. AWS DataSync, rsync, and AWS CLI with concurrent copies all rely on network transfer, which is the limiting factor in this scenario. While DataSync offers features like verification, it cannot overcome the fundamental bandwidth constraint for such a large volume of data within the given timeframe.