managing-wasabi

name	managing-wasabi
description	Use when working with Wasabi — wasabi cloud storage management via the AWS CLI (S3-compatible). Covers buckets, objects, versioning, lifecycle policies, and access control. Use when managing Wasabi storage or reviewing bucket configurations.
connection_type	wasabi
preload	false

Managing Wasabi

Manage Wasabi cloud storage using the AWS CLI with Wasabi-compatible endpoints.

MANDATORY: Discovery-First Pattern

Always discover available resources before performing analysis.

Phase 1: Discovery

#!/bin/bash
export AWS_PAGER=""

WASABI_ENDPOINT="${WASABI_ENDPOINT:-https://s3.wasabisys.com}"

echo "=== Buckets ==="
aws s3api list-buckets --endpoint-url "$WASABI_ENDPOINT" \
    --query 'Buckets[*].[Name,CreationDate]' --output text | head -30

echo ""
echo "=== Bucket Regions ==="
for bucket in $(aws s3api list-buckets --endpoint-url "$WASABI_ENDPOINT" --query 'Buckets[*].Name' --output text); do
    region=$(aws s3api get-bucket-location --bucket "$bucket" --endpoint-url "$WASABI_ENDPOINT" --query 'LocationConstraint' --output text 2>/dev/null)
    echo "$bucket	$region"
done | head -20

Phase 2: Analysis

#!/bin/bash
export AWS_PAGER=""

WASABI_ENDPOINT="${WASABI_ENDPOINT:-https://s3.wasabisys.com}"
BUCKET_NAME="${1:?Bucket name required}"

echo "=== Bucket Objects (sample) ==="
aws s3api list-objects-v2 --bucket "$BUCKET_NAME" --max-items 20 \
    --endpoint-url "$WASABI_ENDPOINT" \
    --query 'Contents[*].[Key,Size,LastModified,StorageClass]' --output text | head -20

echo ""
echo "=== Bucket Size Summary ==="
aws s3 ls "s3://$BUCKET_NAME" --summarize --recursive --endpoint-url "$WASABI_ENDPOINT" 2>/dev/null | tail -3

echo ""
echo "=== Versioning ==="
aws s3api get-bucket-versioning --bucket "$BUCKET_NAME" \
    --endpoint-url "$WASABI_ENDPOINT" --output text

echo ""
echo "=== Lifecycle Rules ==="
aws s3api get-bucket-lifecycle-configuration --bucket "$BUCKET_NAME" \
    --endpoint-url "$WASABI_ENDPOINT" \
    --query 'Rules[*].[ID,Status,Prefix]' --output text 2>/dev/null || echo "No lifecycle rules"

echo ""
echo 
aws s3api get-bucket-policy --bucket  \
    --endpoint-url  --output text 2>/dev/null | jq  |  -15 ||  

 
 
aws s3api get-bucket-cors --bucket  \
    --endpoint-url  \
    --query  --output text 2>/dev/null ||  

 
 
aws s3api get-bucket-acl --bucket  \
    --endpoint-url  \
    --query  --output text

Output Format

BUCKET           REGION        OBJECTS    TOTAL_SIZE
my-backups       us-east-1     12450      2.5TB
media-assets     eu-central-1  89340      500GB

Safety Rules

• Use read-only commands: list-*, get-*, ls
• Never run delete-*, put-*, rm without explicit user confirmation
• Always include --endpoint-url for Wasabi endpoints
• Include export AWS_PAGER="" at script start
• Limit output with | head -N to stay under 50 lines

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations

Shortcut	Counter	Why
"I'll skip discovery and check known resources"	Always run Phase 1 discovery first	Resource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"	Follow the full discovery → analysis flow	Quick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"	Audit configuration explicitly	Defaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"	Always check relevant metrics when available	API/CLI responses show current state; metrics reveal trends and intermittent issues
"I don't have access to that"	Try the command and report the actual error	Assumed permission failures prevent useful investigation; actual errors are informative