# Using Requester Pays general purpose buckets for storage transfers and usage
In general, bucket owners pay for all Amazon S3 storage and data transfer costs that are associated with their bucket. However, you can configure a general purpose bucket to be a *Requester Pays* bucket. With Requester Pays buckets, the requester instead of the bucket owner pays the cost of the request and the data download from the bucket. The bucket owner always pays the cost of storing data.
Typically, you configure buckets to be Requester Pays buckets when you want to share data but not incur charges associated with others accessing the data. For example, you might use Requester Pays buckets when making available large datasets, such as zip code directories, reference data, geospatial information, or web crawling data.
**Important**
If you enable Requester Pays on a general purpose bucket, anonymous access to that bucket is not allowed.
You must authenticate all requests involving Requester Pays buckets. The request authentication enables Amazon S3 to identify and charge the requester for their use of the Requester Pays bucket.
When the requester assumes an AWS Identity and Access Management (IAM) role before making their request, the account to which the role belongs is charged for the request. For more information about IAM roles, see [IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) in the *IAM User Guide*.
After you configure a bucket to be a Requester Pays bucket, requesters must show they understand that they will be charged for the request and for the data download. To show they accept the charges, requesters must either include `x-amz-request-payer` as a header in their API request for DELETE, GET, HEAD, POST, and PUT requests, or add the `RequestPayer` parameter in their REST request. For CLI requests, requesters can use the `--request-payer` parameter.
**Example – Using Requester Pays when deleting an object**
To use the following [https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html) API example, replace the `user input placeholders` with your own information.
```
DELETE /Key+?versionId=VersionId HTTP/1.1
Host: Bucket.s3.amazonaws.com
x-amz-mfa: MFA
x-amz-request-payer: RequestPayer
x-amz-bypass-governance-retention: BypassGovernanceRetention
x-amz-expected-bucket-owner: ExpectedBucketOwner
```
If the requester restores objects by using the [https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html](https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html) API, Requester Pays is supported as long as the `x-amz-request-payer` header or the `RequestPayer` parameter are in the request; however, the requester only pays for the cost of the request. The bucket owner pays the retrieval charges.
Requester Pays buckets do not support the following:
+ Anonymous requests
+ SOAP requests
+ Using a Requester Pays bucket as the target bucket for end-user logging, or vice versa. However, you can turn on end-user logging on a Requester Pays bucket where the target bucket is not a Requester Pays bucket.
## How Requester Pays charges work
The charge for successful Requester Pays requests is straightforward: The requester pays for the data transfer and the request, and the bucket owner pays for the data storage. However, the bucket owner is charged for the request under the following conditions:
+ The request returns an `AccessDenied` (HTTP `403 Forbidden`) error and the request is initiated inside the bucket owner's individual AWS account or AWS organization.
+ The request is a SOAP request.
For more information about Requester Pays, see the following topics.
**Topics**
+ [
## How Requester Pays charges work
](#ChargeDetails)
+ [
# Configuring Requester Pays on a bucket
](RequesterPaysExamples.md)
+ [
# Retrieving the requestPayment configuration using the REST API
](BucketPayerValues.md)
+ [
# Downloading objects from Requester Pays buckets
](ObjectsinRequesterPaysBuckets.md)
# Configuring Requester Pays on a bucket
You can configure an Amazon S3 bucket to be a *Requester Pays* bucket so that the requester pays the cost of the request and data download instead of the bucket owner.
This section provides examples of how to configure Requester Pays on an Amazon S3 bucket using the console and the REST API.
## Using the S3 console
**To enable Requester Pays for an S3 general purpose bucket**
1. Sign in to the AWS Management Console and open the Amazon S3 console at [https://console.aws.amazon.com/s3/](https://console.aws.amazon.com/s3/).
1. In the left navigation pane, choose **General purpose buckets**.
1. In the **General purpose buckets** list, choose the name of the bucket that you want to enable Requester Pays for.
1. Choose **Properties**.
1. Under **Requester pays**, choose **Edit**.
1. Choose **Enable**, and choose **Save changes**.
Amazon S3 enables Requester Pays for your bucket and displays your **Bucket overview**. Under **Requester pays**, you see **Enabled**.
## Using the REST API
Only the bucket owner can set the `RequestPaymentConfiguration.payer` configuration value of a bucket to `BucketOwner` (the default) or `Requester`. Setting the `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 `BucketOwner` 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**
+ Use a `PUT` request to set the `Payer` value to `Requester` on a specified bucket.
```
1. PUT ?requestPayment HTTP/1.1
2. Host: [BucketName].s3.amazonaws.com
3. Content-Length: 173
4. Date: Wed, 01 Mar 2009 12:00:00 GMT
5. Authorization: AWS [Signature]
6.
7.
8. Requester
9.
```
If the request succeeds, Amazon S3 returns a response similar to the following.
```
1. HTTP/1.1 200 OK
2. x-amz-id-2: [id]
3. x-amz-request-id: [request_id]
4. Date: Wed, 01 Mar 2009 12:00:00 GMT
5. Content-Length: 0
6. Connection: close
7. Server: AmazonS3
8. x-amz-request-charged:requester
```
You can set Requester Pays only at the bucket level. You can't set Requester Pays for specific objects within the bucket.
You can configure a bucket to be `BucketOwner` or `Requester` at any time. However, there might be a few minutes before the new configuration value takes effect.
**Note**
Bucket owners who give out presigned URLs should consider carefully before configuring a bucket to be Requester Pays, especially if the URL has a long lifetime. The bucket owner is charged each time the requester uses a presigned URL that uses the bucket owner's credentials.
# Retrieving the requestPayment configuration using the REST API
You can determine the `Payer` value that is set on a bucket by requesting the resource `requestPayment`.
**To return the requestPayment resource**
+ Use a GET request to obtain the `requestPayment` resource, as shown in the following request.
```
1. GET ?requestPayment HTTP/1.1
2. Host: [BucketName].s3.amazonaws.com
3. Date: Wed, 01 Mar 2009 12:00:00 GMT
4. Authorization: AWS [Signature]
```
If the request succeeds, Amazon S3 returns a response similar to the following.
```
1. HTTP/1.1 200 OK
2. x-amz-id-2: [id]
3. x-amz-request-id: [request_id]
4. Date: Wed, 01 Mar 2009 12:00:00 GMT
5. Content-Type: [type]
6. Content-Length: [length]
7. Connection: close
8. Server: AmazonS3
9.
10.
11.
12. Requester
13.
```
This response shows that the `payer` value is set to `Requester`.
# Downloading objects from Requester Pays buckets
Because requesters are charged for downloading data from Requester Pays buckets, the requests must contain a special parameter, `x-amz-request-payer`, which confirms that the requester knows that they will be charged for the download. To access objects in Requester Pays buckets, requests must include one of the following.
+ For DELETE, GET, HEAD, POST, and PUT requests, include `x-amz-request-payer : requester` in the header
+ For signed URLs, include `x-amz-request-payer=requester` in the request
If the request succeeds and the requester is charged, the response includes the header `x-amz-request-charged:requester`. If `x-amz-request-payer` is not in the request, Amazon S3 returns a 403 error and charges the bucket owner for the request.
**Note**
Bucket owners do not need to add `x-amz-request-payer` to their requests.
Ensure that you have included `x-amz-request-payer` and its value in your signature calculation. For more information, see [Using an Authorization Header](https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html) in the *Amazon S3 API Reference* .
## Using the REST API
**To download objects from a Requester Pays bucket**
+ Use a `GET` request to download an object from a Requester Pays bucket, as shown in the following request.
```
1. GET / [destinationObject] HTTP/1.1
2. Host: [BucketName].s3.amazonaws.com
3. x-amz-request-payer : requester
4. Date: Wed, 01 Mar 2009 12:00:00 GMT
5. Authorization: AWS [Signature]
```
If the GET request succeeds and the requester is charged, the response includes `x-amz-request-charged:requester`.
Amazon S3 can return an `Access Denied` error for requests that try to get objects from a Requester Pays bucket. For more information, see [Error Responses](https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html) in the *Amazon Simple Storage Service API Reference*.
## Using the AWS CLI
To download objects from a Requester Pays bucket using the AWS CLI, you specify `--request-payer requester` as part of your `get-object` request. For more information, see [get-object](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/get-object.html) in the *AWS CLI Reference*.