GetBucketRequestPayment

GetBucketRequestPayment reports a bucket's request payment configuration: who pays for the requests and downloads made against it. On STRG only stored data is billed - there are no request or download fees for anyone to pay - so the answer is simple: the operation checks that the bucket exists and always answers BucketOwner. Requester Pays buckets have nothing to do here, which means a client never needs to send anything extra to read from a bucket.

Good to know on STRG

• The answer is always <Payer>BucketOwner</Payer>; Requester never appears.
• PutBucketRequestPayment is answered with 501 NotImplemented, so a client knows straight away.
• x-amz-expected-bucket-owner is welcome and has nothing to check: a key only ever reaches buckets of its own account.

When you'd use it

• Tools that describe a bucket. Infrastructure-as-code tools and inventory scripts written for Amazon S3 read every bucket setting they know about, request payment included. On STRG the request succeeds with BucketOwner, so the description completes without errors.
• Download tools that check for Requester Pays first. A client that looks up who pays before deciding whether to send x-amz-request-payer: requester learns that the bucket owner does, and downloads as usual.
• Audits of bucket settings. A compliance script that checks no bucket bills its readers gets the same clear answer for every bucket.

Request

GET /?requestPayment HTTP/1.1
Host: my-bucket.s3.eu-central-1.strg.com
Authorization: AWS4-HMAC-SHA256 Credential=...
x-amz-date: 20260926T120000Z
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

The path-style form is GET /my-bucket?requestPayment on s3.eu-central-1.strg.com - Addressing explains both.

Permissions

The access key needs Read bucket settings (buckets:read-config). Every access key holds it, whether it covers all buckets or only some - a key scoped to specific buckets reads only those. Access keys has the details.

URI parameters

Name	Type	Required	Description
Bucket	String	Yes	The bucket whose request payment configuration to read.
requestPayment	Flag	Yes	Selects this operation. Sent with no value.

Any other query parameter is answered with 501 NotImplemented, so a client knows straight away that it has no effect here.

Request headers

Name	Type	Required	Description
x-amz-expected-bucket-owner	String	No	Welcome, with nothing to check: an access key only ever reaches its own account's buckets.

Request body

None.

Response

A successful request answers 200 OK with an XML body.

Response headers

Name	Description
Content-Type	application/xml.
x-amz-request-id	The request ID, handy for a support request.

Response body

The document has one element, and its value never changes:

Element	Type	Description
RequestPaymentConfiguration	Container	The root element.
Payer	String	Who pays for requests and downloads. Always BucketOwner on STRG.

<?xml version="1.0" encoding="UTF-8"?>
<RequestPaymentConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Payer>BucketOwner</Payer></RequestPaymentConfiguration>

Errors

These are the errors this request can return, and the situation behind each one.

Code	HTTP status	When
NoSuchBucket	404	The bucket does not exist, belongs to another account, is in a region other than the endpoint's, or the account stores nothing in the endpoint's region yet.
AccessDenied	403	The access key is scoped to buckets that do not include this one, or the account is not active.
InvalidAccessKeyId	403	The access key does not exist, has expired or been revoked - or it was created moments ago and is not usable yet in a region where the account already stores data, in which case the same request works shortly afterwards.
SignatureDoesNotMatch	403	The request signature does not match.
RequestTimeTooSkewed	403	The request time is more than 15 minutes from the server's.
AuthorizationHeaderMalformed	400	The signature's credential scope names a region other than the endpoint's.
NotImplemented	501	The request carries a query parameter this operation does not accept.
SlowDown	503	Too many requests. The Retry-After header says when a retry is welcome; the AWS SDKs retry on their own.
ServiceUnavailable	503	A temporary failure; the same request can be retried.
InternalError	500	An unexpected failure while checking the bucket; the same request can be retried.

Differences from Amazon S3

The table lists each place where STRG behaves differently, and what that means for a client.

Aspect	Amazon S3	STRG
Payer	BucketOwner or Requester, as configured	Always BucketOwner. There are no request or download fees, so there is no one else to bill
Setting it	PutBucketRequestPayment	Answered with 501 NotImplemented
Bucket in another region	301 redirect with x-amz-bucket-region	404 NoSuchBucket. A bucket is reached through its own regional endpoint.
x-amz-expected-bucket-owner	Checked against the bucket owner	Welcome, with nothing to check

Examples

Reading the request payment configuration of my-bucket in eu-central-1:

AWS CLI

aws s3api get-bucket-request-payment \
  --bucket my-bucket \
  --endpoint-url https://s3.eu-central-1.strg.com \
  --region eu-central-1

The command prints:

{
    "Payer": "BucketOwner"
}

Python (boto3)

import boto3

s3 = boto3.client(
    "s3",
    endpoint_url="https://s3.eu-central-1.strg.com",
    region_name="eu-central-1",
)

response = s3.get_bucket_request_payment(Bucket="my-bucket")
print(response["Payer"])  # BucketOwner

JavaScript (AWS SDK v3)

import { GetBucketRequestPaymentCommand, S3Client } from "@aws-sdk/client-s3";

const client = new S3Client({
  endpoint: "https://s3.eu-central-1.strg.com",
  region: "eu-central-1",
});

const response = await client.send(
  new GetBucketRequestPaymentCommand({ Bucket: "my-bucket" }),
);
console.log(response.Payer); // BucketOwner

Related

• GetBucketAccelerateConfiguration
• GetBucketLocation
• GetBucketVersioning
• Access keys
• S3 API overview - including the other S3 operations