Buckets

Buckets are top-level containers for objects. Use naming and structure that stays clean long-term.

Recommended bucket naming

Use lowercase, hyphens, and business-friendly names. Avoid underscores and spaces.

backups — server & client backups
media — images, audio, video assets
logs-archive — long-term log storage
datasets — analytics & dataset exports

Folder patterns (prefix strategy)

S3 uses object keys (prefixes) to simulate folders. Standardize them early.

backups/
  srv1/
    2025-12-25/
  srv2/
    2025-12-25/
clients/
  acme.com/
    daily/
    weekly/

Create & list buckets (AWS CLI)

Use the endpoint URL to target MigraDrive.

export AWS_ACCESS_KEY_ID="REPLACE_ME"
export AWS_SECRET_ACCESS_KEY="REPLACE_ME"
export AWS_DEFAULT_REGION="us-east-1"

# list buckets
aws s3 ls --endpoint-url "https://s3.migradrive.com"

# create bucket (example)
aws s3 mb s3://backups --endpoint-url "https://s3.migradrive.com"

# list objects in a bucket
aws s3 ls s3://backups --endpoint-url "https://s3.migradrive.com"

Public vs private buckets

Default should be private. If you need public access, prefer presigned URLs over public buckets.

Private by default: best for backups and customer data
Public assets: use a dedicated bucket + strict policy + CDN (optional later)
Safer approach: use presigned URLs for time-limited downloads