Create the buckets

Progress checklist

• Standard general-purpose bucket exists
• Directory bucket named with --apse2-az1--x-s3
• Both buckets tagged with the lab Project tag

Overview

Two buckets in ap-southeast-2 — a Standard general-purpose bucket (baseline) and a directory-bucketdirectory-bucket
S3 bucket type that hosts the S3 Express One Zone storage class. Names follow bucket-base-name--zone-id--x-s3 and live in a single Availability Zone. for S3 Express One ZoneS3 Express One Zone
Amazon S3 Express One Zone — single-AZ storage class optimized for consistent single-digit millisecond latency, used only with directory buckets.
S3 Express One Zone. Directory names follow bucket-base-name--zone-id--x-s3; this lab uses AZ ID apse2-az1 only.

Bucket	Naming
Standard	s3x-hotlookup-${LAB_SUFFIX}-${ACCOUNT_ID}
Directory	s3x-hotlookup-${LAB_SUFFIX}--apse2-az1--x-s3

Caution

S3 storage and request charges apply until you empty and delete both buckets. See S3 pricing rather than hardcoding rates.

Steps

Reuse the same LAB_SUFFIX as the VPC. Run from the repo root.

export AWS_PROFILE=sandbox
export AWS_REGION=ap-southeast-2
export S3X_LAB_ALLOW_AWS=1
export LAB_SUFFIX=${LAB_SUFFIX:-$(date +%Y%m%d%H%M%S)}
export ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
export STD_BUCKET="s3x-hotlookup-${LAB_SUFFIX}-${ACCOUNT_ID}"
export DIR_BUCKET="s3x-hotlookup-${LAB_SUFFIX}--apse2-az1--x-s3"
echo "STD_BUCKET=${STD_BUCKET}"
echo "DIR_BUCKET=${DIR_BUCKET}"

Looks like (verified shape; suffix and account are yours):

STD_BUCKET=s3x-hotlookup-EXAMPLE-123456789012
DIR_BUCKET=s3x-hotlookup-EXAMPLE--apse2-az1--x-s3

1. Create the Standard general-purpose bucket.

   aws s3api create-bucket \
     --bucket "$STD_BUCKET" \
     --create-bucket-configuration "LocationConstraint=${AWS_REGION}"

   Looks like (verified shape):

   {
     "Location": "<standard regional endpoint URL for STD_BUCKET>",
     "BucketArn": "arn:aws:s3:::s3x-hotlookup-EXAMPLE-123456789012"
   }

2. Tag the Standard bucket with the lab Project tag.

   aws s3api put-bucket-tagging \
     --bucket "$STD_BUCKET" \
     --tagging 'TagSet=[{Key=Project,Value=s3-express-hot-lookup-walkthrough}]'

   Looks like: no stdout on success (exit 0).

3. Create the directory bucket with Location Type=AvailabilityZone.

   aws s3api create-bucket \
     --bucket "$DIR_BUCKET" \
     --create-bucket-configuration '{
       "Location": {
         "Type": "AvailabilityZone",
         "Name": "apse2-az1"
       },
       "Bucket": {
         "DataRedundancy": "SingleAvailabilityZone",
         "Type": "Directory"
       }
     }' \
     --region "$AWS_REGION"

   Looks like (verified shape):

   {
     "Location": "<zonal Express endpoint URL for DIR_BUCKET>",
     "BucketArn": "arn:aws:s3express:ap-southeast-2:123456789012:bucket/s3x-hotlookup-EXAMPLE--apse2-az1--x-s3"
   }

   Tip

   The name suffix —apse2-az1—x-s3 must match the AZ ID in Location.Name. Do not invent a second Sydney Express AZ — only apse2-az1 is supported.

4. Tag the directory bucket (S3 Control TagResource — classic put-bucket-tagging is not supported on directory buckets).

   aws s3control tag-resource \
     --account-id "$ACCOUNT_ID" \
     --resource-arn "arn:aws:s3express:${AWS_REGION}:${ACCOUNT_ID}:bucket/${DIR_BUCKET}" \
     --tags Key=Project,Value=s3-express-hot-lookup-walkthrough

   Looks like: no stdout on success (exit 0).

Prefer the wrapper

demo.sh up creates both buckets (plus VPC, IAM, and EC2) after the harness image from Build harness image:

export S3X_LAB_ALLOW_AWS=1
./scripts/demo.sh up

Verify

1. Standard bucket location and tags.

   aws s3api get-bucket-location --bucket "$STD_BUCKET"
   aws s3api get-bucket-tagging --bucket "$STD_BUCKET"

   Looks like (verified):

   {
     "LocationConstraint": "ap-southeast-2"
   }

   {
     "TagSet": [
       {
         "Key": "Project",
         "Value": "s3-express-hot-lookup-walkthrough"
       }
     ]
   }

2. Directory bucket head and tags.

   aws s3api head-bucket --bucket "$DIR_BUCKET"
   aws s3control list-tags-for-resource \
     --account-id "$ACCOUNT_ID" \
     --resource-arn "arn:aws:s3express:${AWS_REGION}:${ACCOUNT_ID}:bucket/${DIR_BUCKET}"

   Looks like (verified shape):

   {
     "BucketArn": "arn:aws:s3express:ap-southeast-2:123456789012:bucket/s3x-hotlookup-EXAMPLE--apse2-az1--x-s3",
     "BucketLocationType": "AvailabilityZone",
     "BucketLocationName": "apse2-az1",
     "BucketRegion": "ap-southeast-2",
     "AccessPointAlias": false
   }

   {
     "Tags": [
       {
         "Key": "Project",
         "Value": "s3-express-hot-lookup-walkthrough"
       }
     ]
   }

3. Print ARNs.

   echo "arn:aws:s3:::${STD_BUCKET}"
   echo "arn:aws:s3express:${AWS_REGION}:${ACCOUNT_ID}:bucket/${DIR_BUCKET}"

   Looks like (verified shape):

   arn:aws:s3:::s3x-hotlookup-EXAMPLE-123456789012
   arn:aws:s3express:ap-southeast-2:123456789012:bucket/s3x-hotlookup-EXAMPLE--apse2-az1--x-s3

Check	Expect
Standard location	ap-southeast-2
Directory name	ends with --apse2-az1--x-s3
Directory location	AvailabilityZone / apse2-az1
Tag (Standard)	s3api get-bucket-tagging → Project=…
Tag (directory)	s3control list-tags-for-resource → Project=…

Next

Continue to IAM and EC2.

References

• Creating directory buckets
• High-performance directory buckets
• Using tags with directory buckets
• S3 Express Regions and Zones
• Differences for directory buckets
• S3 pricing