managing-tigris

name	managing-tigris
description	Use when working with Tigris — tigris globally distributed object storage management via the AWS CLI (S3-compatible) and Tigris dashboard API. Covers buckets, objects, regions, caching, and shadow buckets. Use when managing Tigris storage or reviewing global distribution.
connection_type	tigris
preload	false

Managing Tigris

Manage Tigris object storage using the AWS CLI with Tigris-compatible endpoints.

MANDATORY: Discovery-First Pattern

Always discover available resources before performing analysis.

Phase 1: Discovery

#!/bin/bash
export AWS_PAGER=""

TIGRIS_ENDPOINT="https://fly.storage.tigris.dev"

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

echo ""
echo "=== Bucket Details ==="
for bucket in $(aws s3api list-buckets --endpoint-url "$TIGRIS_ENDPOINT" --query 'Buckets[*].Name' --output text); do
    objects=$(aws s3api list-objects-v2 --bucket "$bucket" --endpoint-url "$TIGRIS_ENDPOINT" --query 'KeyCount' --output text 2>/dev/null)
    echo "$bucket	objects=$objects"
done | head -20

Phase 2: Analysis

#!/bin/bash
export AWS_PAGER=""

TIGRIS_ENDPOINT="https://fly.storage.tigris.dev"
BUCKET_NAME="${1:?Bucket name required}"

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

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

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

echo ""
echo "=== Bucket ACL ==="
aws s3api get-bucket-acl --bucket "$BUCKET_NAME" \
    --endpoint-url "$TIGRIS_ENDPOINT" \
    --query 'Grants[*].[Grantee.Type,Permission]' --output text

echo ""
echo "=== CORS Configuration ==="
aws s3api get-bucket-cors --bucket "$BUCKET_NAME" \
    --endpoint-url  \
    --query  --output text 2>/dev/null ||  

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

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

Output Format

BUCKET           OBJECTS    TOTAL_SIZE    CREATED
cdn-assets       12450      45GB          2024-01-15
app-uploads      890        12GB          2024-02-01

Safety Rules

• Use read-only commands: list-*, get-*, ls
• Never run delete-*, put-*, rm without explicit user confirmation
• Always include --endpoint-url for Tigris 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