Enable Requester Pays on an S3 bucket

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

What we are learning

Requester Pays shifts supported request and data-transfer charges from the bucket owner to an authenticated requester who acknowledges the charge.

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: This setting changes who is billed for supported requests and transfer. Announce it to consumers before enabling it.

aws s3api put-bucket-request-payment \
  --bucket "$BUCKET" \
  --request-payment-configuration Payer=Requester

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

aws s3api get-bucket-request-payment \
  --bucket "$BUCKET" \
  --query Payer \
  --output text

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

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

Supported data requests need the requester acknowledgement when Requester Pays is enabled.

Requester Pays does not make a bucket public and does not transfer every possible bucket cost. Use it only for a deliberate data-sharing model.

aws s3api put-bucket-request-payment \
  --bucket "$BUCKET" \
  --request-payment-configuration Payer=BucketOwner

Return the demo bucket to normal owner-paid behavior.

Next, we will learn Call a Requester Pays S3 bucket.