Wasabi is a hot cloud storage service with no egress fees. This guide walks you through connecting your Wasabi bucket to HeftySend.
Custom storage requires a Premium or Ultra plan. See Using your own storage with HeftySend for an overview.
Step 1: Create your Wasabi bucket
- Go to your Wasabi Console
- Click "Create Bucket"
- Enter a unique bucket name
- Select a region closest to your users
- Click "Create Bucket"
Step 2: Set up CORS
- Click on your bucket name to open it
- Go to the "Settings" tab
- Find "CORS Configuration" and click "Add CORS rule"
- Paste this configuration:
[
{
"AllowedOrigins": ["*"],
"AllowedMethods": ["GET", "PUT", "POST", "DELETE", "HEAD"],
"AllowedHeaders": ["*"],
"ExposeHeaders": ["ETag"],
"MaxAgeSeconds": 3000
}
]
- Click "Save"
CORS must be configured on the bucket or browser uploads will be blocked.
Step 3: Create access keys
- Go to Access Keys in your account
- Click "Create New Access Key"
- Optionally enter a description (for example, HeftySend)
- Click "Create"
Download or copy both the Access Key and Secret Key now. They are only shown once.
Step 4: Connect to HeftySend
- Go to Settings > Storage in your HeftySend dashboard
- Click "Configure S3 Storage"
- Enter your endpoint URL based on your region (see table below)
- Enter your Access Key and Secret Key
- Enter your bucket name
- Click "Test Connection" then "Save"
Wasabi regions and endpoints
| Region | Endpoint |
|---|---|
| us-east-1 | https://s3.wasabisys.com |
| us-east-2 | https://s3.us-east-2.wasabisys.com |
| us-central-1 | https://s3.us-central-1.wasabisys.com |
| us-west-1 | https://s3.us-west-1.wasabisys.com |
| eu-central-1 | https://s3.eu-central-1.wasabisys.com |
| eu-central-2 | https://s3.eu-central-2.wasabisys.com |
| eu-west-1 | https://s3.eu-west-1.wasabisys.com |
| ap-northeast-1 | https://s3.ap-northeast-1.wasabisys.com |
| ap-southeast-1 | https://s3.ap-southeast-1.wasabisys.com |
Troubleshooting
If connection fails, double-check that your endpoint URL matches your bucket's region exactly. Bucket names are case-sensitive.