That’s much better for a source, thanks. Do notice the context, however. We’re approaching this problem from the perspective of trying to determine the network

That’s much better for a source, thanks. Do notice the context, however. We’re approaching this problem from the perspective of trying to determine the network bandwidth of a portable datacenter driving down the highway. Assuming that container is really just a giant USB harddrive then it’s 10 days for copy at client’s site, 8 hours for the drive, and then another 10 days to assimilate the data back at AWS DC, or more if pushing it to 2 other DCs is slower. Perhaps there’s some way to alleviate some of those concerns by shipping minimal S3-API server in the Snowmobile, then deploy actual production code when it’s assimilated back home. Perhaps the Snowmobile could become its own region temporarily. Still, you’re right that is a lot of moving parts for something that you’d want to avoid… Except in this extremely important hypothetical, obviously. Also, while it is probably true that S3 has way more storage distributed across the globe, I think the Snowmobile still follows the Sat Nav not DNS & BGP ;) I mean it delivers to a single DC, so that’s what needs to be considered. Actually 100 PB is a lot on disk, but it’s even more over the network. They’ll probably want to push it during off-peaks, but should probably consider to just keep driving the truck to the next AZ.