Setting the requestPayment Bucket Configuration
Only the bucket owner can set the
RequestPaymentConfiguration.payer configuration value
of a bucket to
BucketOwner, the default, or
requestPayment resource is optional. By
default, the bucket is not a Requester Pays bucket.
To revert a Requester Pays bucket to a regular bucket, you use the value
BucketOwner. Typically, you would use
when uploading data to the Amazon S3 bucket, and then you would set the value to
Requester before publishing the objects in the bucket.
To set requestPayment
PUTrequest to set the
Requesteron a specified bucket.
PUT ?requestPayment HTTP/1.1 Host:
[BucketName].s3.amazonaws.com Content-Length: 173 Date: Wed, 01 Mar 2009 12:00:00 GMT Authorization: AWS
[Signature]<RequestPaymentConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Payer>Requester</Payer> </RequestPaymentConfiguration>
If the request succeeds, Amazon S3 returns a response similar to the following.
HTTP/1.1 200 OK x-amz-id-2: [id] x-amz-request-id: [request_id] Date: Wed, 01 Mar 2009 12:00:00 GMT Content-Length: 0 Connection: close Server: AmazonS3 x-amz-request-charged:requester
You can set Requester Pays only at the bucket level; you cannot set Requester Pays for specific objects within the bucket.
You can configure a bucket to be
Requester at any time. Realize, however, that there might be a
small delay, on the order of minutes, before the new configuration value takes
Bucket owners who give out pre-signed URLs should think twice before configuring a bucket to be Requester Pays, especially if the URL has a very long lifetime. The bucket owner is charged each time the requester uses a pre-signed URL that uses the bucket owner's credentials.