Browse Teach Curate

Who Pays When a Collaborator Downloads Your Result: Egress and Requester-Pays

The outcome ends with a result someone else can re-derive, which means someone else fetching data. The asymmetry between inbound and outbound transfer is invisible to a researcher used to copying files across a lab network, and it is the surprise that turns a generous sharing decision into an unbudgeted bill. It is required for the sharing step of the outcome to be costed rather than merely performed.

jeremy Video

Shifting Data Transfer Charges to Downloaders with Requester Pays Buckets in Amazon S3

Requester Pays is a cost-attribution mechanism in Amazon S3 object storage that inverts the default billing party for data egress: instead of the bucket owner bearing both storage and data-transfer c…