Connecting Wasabi
This guide walks you through connecting a Wasabi Hot Cloud Storage destination to Pluton.
Prerequisites
Before connecting Wasabi, you need:
- A Wasabi account - Sign up here
- Access Keys (Access Key ID and Secret Access Key)
- A bucket created in your desired region
Getting Your Wasabi Credentials
Step 1: Create Access Keys
- Log into the Wasabi Console
- Click Access Keys in the left sidebar
- Click Create New Access Key
- Important: Download or copy both the Access Key ID and Secret Access Key immediately — the Secret Key is shown only once
Step 2: Create a Bucket
- Go to Buckets in the Wasabi Console
- Click Create Bucket
- Enter a bucket name and select a region (e.g., us-east-1, eu-central-1)
- Configure versioning and logging settings as needed
- Click Create Bucket
Connecting to Pluton

Step 1: Add Storage
- In Pluton, navigate to Storages
- Click Add Storage button
- Select Wasabi from the provider list
Step 2: Configure Connection
Fill in the required fields:
- Storage Name: A friendly name (e.g., "Wasabi Backups")
- Access Key ID: Your Wasabi Access Key ID
- Secret Access Key: Your Wasabi Secret Access Key (password)
- Region: Select the region where your bucket is located (e.g., US East 1, EU Central 1, AP Northeast 1)
Step 3: Advanced Options (Optional)
Additional settings available:
- ACL: Set access control for objects (Private, Public Read, Authenticated Read, etc.)
- Server-side Encryption: Choose AES256 or KMS encryption for data at rest
- Storage Class: Select the storage tier for your objects
- Chunk Size: Adjust the chunk size for multipart uploads (default: 5 MiB)
- Upload Cutoff: Set the threshold for switching to chunked uploads (default: 200 MiB)
- Force Path Style: Enable path-style access instead of virtual hosted-style
Step 4: Test and Save
- Click Test Connection to verify credentials
- If successful, click Save
- Your Wasabi storage is now ready for backup plans
Common Issues
Region Mismatch: Wasabi requires the correct region for your bucket. Each region has a distinct endpoint (e.g., s3.us-east-1.wasabisys.com). Ensure you select the region matching your bucket.
Access Denied: Verify your Access Keys have the necessary permissions. Wasabi access keys have full account access by default, but IAM policies can restrict them.
Bucket Not Found: Ensure the bucket name is correct and exists in the selected region. Bucket names are globally unique across Wasabi.
Best Practices
- Wasabi has no egress fees, making it ideal for backups that require frequent restores
- Use Wasabi's bucket versioning for additional data protection
- Create separate buckets per backup plan for better organization
- Enable Wasabi's immutability (Object Lock) features for ransomware protection