Giving you an option to only bulk egress is not the same either, since the most common scenario for egress would be operational day-to-day inter-network scenarios.
If there is an unreasonably high fee for exiting a provider's cloud, to any other network location, on an operational basis, it is actively discouraging exiting the provider's services creating a kind of price barrier that could be cost prohibitive for operational inter-networking.
Operational inter-networking, to me, encourages competition not discourages it.
For example, perhaps I want to use Microsoft Azure's Data Factory to move data from AWS S3 to Redshift. It is not possible as far as I know without egress from AWS to Microsoft's network, and then back again. But surely these clouds are connected with peering relationships making the cost of ingress/egress negligible, so why is this not allowed? That would allow users of the cloud to freely mix and match services from among many clouds.
The world I see today does not seem to encourage such competition.
Apple did the same thing with Webkit. Google came onboard and for awhile, everyone was releasing Webkit compatible browsers.
1. That fee is in addition to S3 retrieval costs.
> Q: What does it cost to export my data?
> In addition to the Export job fees detailed on our pricing page, you will also be charged all fees incurred to retrieve your data from Amazon S3.
https://aws.amazon.com/snowball/faqs/
2. $30/TB isn’t even cheap by itself.
S3 request fees are $.0004 per 1000 GET requests. If you had 100000 objects (files) you would pay $40
If you have a massive amount of data, you can always get AWS to transfer it to you via a Snowball for $30/TB + a $300 fee.