Enable S3 Transfer Acceleration

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

What we are learning

Transfer Acceleration routes transfers through AWS edge locations. It is useful only when measurements justify the added cost.

Before you run it

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: Accelerated transfer has additional pricing. Benchmark from real client locations before enabling it permanently.

The command

aws s3api put-bucket-accelerate-configuration \
  --bucket "$BUCKET" \
  --accelerate-configuration Status=Enabled

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

Inspect the result

aws s3api get-bucket-accelerate-configuration \
  --bucket "$BUCKET" \
  --query Status \
  --output text

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

One tiny variation

aws s3api put-bucket-accelerate-configuration \
  --bucket "$BUCKET" \
  --accelerate-configuration Status=Suspended

Suspending disables accelerated endpoint use without deleting the bucket.

Common mistake

Buckets with dots in their names are not compatible with Transfer Acceleration endpoint certificate requirements. Check naming before designing around acceleration.

Cleanup

aws s3api put-bucket-accelerate-configuration \
  --bucket "$BUCKET" \
  --accelerate-configuration Status=Suspended

Leave the demo bucket suspended after the lesson.

Next, we will learn Use the S3 accelerated endpoint from AWS CLI.

Official AWS CLI reference