>"Access to S3 is zero-rated in many cases with S3, however the real advantage comes when you are using this cross-region." Or cross-Country... as in two Count

>"Access to S3 is zero-rated in many cases with S3, however the real advantage comes when you are using this cross-region." Or cross-Country... as in two Countries that are geoblocked from one another... >"This lets you have a worker in us-east-1 communicate with another worker in us-west-1 without having to incur the high bandwidth cost per gigabyte when using Managed NAT Gateway." Simplified algorithm for bypassing geoblock via the above method: 1) Select a cloud storage provider (could be any cloud storage provider or shared persistent storage platform; doesn't necessarily need to be Amazon/S3) that works or does business in two countries, Country A and Country B, where normal IP traffic is geoblocked between Country A and Country B. 2) Use shared cloud storage objects/buckets/rows (call them whatever you will, "keyed persistent storage discrete thingies" for lack of a better term!) as the article suggests, to emulate IP traffic between user A in Country A and user B in blocked country B... 3) Combined with a P2P or other front end app that knows how to use this method of communication (along with code stubs, such that people could customize it to their own cloud storage provider or platform) if/when normal country-to-country IP communication is blocked for whatever reason (zombie apocalypse? <g>) could make a powerful future P2P communications tool, for lawful purposes... Anyway, great article!