Skip to content

Instantly share code, notes, and snippets.

@ryanlong1004
Last active May 22, 2025 19:27
Show Gist options
  • Save ryanlong1004/45fa482bc3228b520effe6d9753c3503 to your computer and use it in GitHub Desktop.
Save ryanlong1004/45fa482bc3228b520effe6d9753c3503 to your computer and use it in GitHub Desktop.
Use AWS CLI with WASABI

WASABI AWS CLI SETUP


βœ… Step-by-Step Instructions to Use Wasabi with AWS CLI

πŸ”Ή 1. Create Wasabi Access Keys

  • Go to your Wasabi console and create a new access key.

  • Save the following securely:

    • Access Key: **********
    • Secret Key: ************************************

πŸ”Ή 2. Configure AWS CLI with Wasabi Profile

In your terminal, run:

aws configure --profile wasabi

Enter the following when prompted:

  • AWS Access Key ID: *******************
  • AWS Secret Access Key: **************************
  • Default region name: us-east-1
  • Default output format: json

βœ… This creates a named profile wasabi in your ~/.aws/credentials and ~/.aws/config.


πŸ”Ή 3. List Contents of a Wasabi S3 Bucket

Use the AWS CLI with a custom endpoint URL for Wasabi:

aws s3 ls s3://<bucket-name-only> --endpoint-url=https://s3.wasabisys.com --profile wasabi

This will return a file listing similar to:

2024-08-29 14:52:17   12265306 file1.m4v
2024-09-23 16:05:09   29653097 file2.mp4

πŸ“Œ Note: Wasabi is S3-compatible but requires the --endpoint-url=https://s3.wasabisys.com flag.


πŸ›  Troubleshooting Tips

  • If you see Access Denied:

    • Double-check the bucket permissions.
    • Ensure the access key has permission to list/read the bucket (s3:ListBucket, s3:GetObject).
    • Validate bucket region (e.g., if using us-east-1, make sure the bucket was created in that region).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment