Call a Requester Pays S3 bucket

Part 64 of AWS from Zero. This lesson keeps the scope to one S3 behavior you can verify from the terminal.

What we are learning

The requester must authenticate and explicitly acknowledge payment on supported operations.

aws sts get-caller-identity
REGION="ap-south-1"
BUCKET="replace-with-your-private-demo-bucket"

Use a private general purpose bucket that you own. Replace every placeholder before running a write or delete command.

Cost note: The credentials used for the request can incur supported request and transfer charges.

aws s3api list-objects-v2 \
  --bucket "$BUCKET" \
  --request-payer requester

A successful configuration command may return no output. Treat inspection as a separate required step.

aws s3api head-object \
  --bucket "$BUCKET" \
  --key shared/data.csv \
  --request-payer requester

Read the returned fields rather than assuming the write succeeded exactly as intended.

aws s3api get-object \
  --bucket "$BUCKET" \
  --key shared/data.csv \
  --request-payer requester   data.csv

The same acknowledgement is needed when retrieving the object body.

Leaving out --request-payer requester can produce AccessDenied even when the identity otherwise has permission.

rm data.csv 2>/dev/null || true

Only the optional local download is removed. Do not change the bucket setting unless you own its billing model.

Next, we will learn Enable S3 Transfer Acceleration.