Which one is the correct requester or requester

Consume buckets with payment by the requester for storage transfers and usage

In general, bucket owners pay any Amazon S3 storage and data transfer costs associated with their bucket. However, you can use a bucket as a bucket Payment by the requester configure. In the case of buckets with payment by the requester, the client pays the costs for the request and the data download from the bucket instead of the bucket owner. The bucket owner always pays the cost of storing the data.

Typically, you configure buckets to be paid for by the requester when you want to share data but don't want to pay for it when others access the data. For example, you can use requester-paid buckets if you are serving large datasets such as zip codes, reference data, geospatial information, or web crawling data.

If you enable payment by the requester for a bucket, anonymous access to the bucket is not allowed.

You must authenticate all requests for payment-by-requester buckets. Request authentication enables Amazon S3 to identify the requester and to bill him for his use of the bucket with payment by the requester.

If a requester assumes an AWS Identity and Access Management (IAM) role before making the request, the account that the role belongs to will be charged for the request. For more information about IAM roles, see IAM roles in the IAM User Guide.

After you have configured a bucket as a bucket with payment by the requester, the requesters must include them in their requests, either in the header if it is POST, GET and HEAD requests, or as a parameter in a REST request, to demonstrate that they know they will be billed for the request and data download fees.

Requester paid buckets do not support the following features:

  • Anonymous requests

  • Bit torrent

  • SOAP requirements

  • The use of a payment bucket by the requester as the destination bucket for end-user logging, or vice versa. However, you can enable end-user logging for a requester paid bucket if the destination bucket is not a requester paid bucket.

The fees when paid by the requester

The distribution of the charges for successful requests with payment by the requester is very simple: the requester pays for the data transfer and the request, the bucket owner pays for the storage of the data. However, the bucket owner will only be charged for the request under the following conditions:

  • The client does not specify the parameter in the header (GET, HEAD or POST) or as a parameter (REST) ​​in the request (HTTP code 403).

  • The authentication of the request fails (HTTP code 403).

  • the request is anonymous (HTTP code 403).

  • the request is a SOAP request.

For more information about payment by the requester, see the following topics.