Wasabi

Back up signed PDFs to Wasabi — an S3-compatible service with no egress fees and predictable pricing.

Tip

Wasabi uses the same S3 API as Amazon. The only difference is the endpoint and available regions.

---

Requirements

• WPsigner 2.1.0+
• A Wasabi account
• Access key and secret key from the Wasabi console

---

How It Works

When a signer completes a document, WPsigner automatically uploads the final PDF to your Wasabi bucket. The flow is identical to the Amazon S3 integration because Wasabi implements the same S3 API:

1. Document signed — All required signers complete the document.
2. PDF generated — WPsigner creates the final certified PDF.
3. Upload triggered — The plugin sends the PDF to your Wasabi bucket using the S3 PutObject operation with AWS Signature V4 authentication.
4. Confirmation stored — WPsigner records the remote URL and upload status in the document metadata.

Note

Uploads happen server-side in the background. Signers are not affected by the upload process and receive their confirmation immediately.

---

Setup

Step 1: Create a Bucket

1. Go to the Wasabi Console.
2. Click Create Bucket.
3. Choose a unique bucket name (lowercase, no spaces). Example: wpsigner-signed-docs.
4. Select the region closest to your WordPress server for the best upload performance.
5. Leave versioning and logging at their defaults unless your organization requires them.
6. Click Create Bucket.

Caution

Bucket names are globally unique across all Wasabi accounts. If the name is already taken, you will need to choose a different one.

Step 2: Create Access Keys

1. Go to Access Keys in the Wasabi console sidebar.
2. Click Create New Access Key.
3. Copy both the Access Key and Secret Key immediately — the secret key is shown only once.

Store these credentials in a secure location. If you lose the secret key, you must generate a new key pair.

Step 3: Configure WPsigner

1. Go to WPsigner → Integrations → Wasabi in your WordPress admin.
2. Enter the Access Key and Secret Key from Step 2.
3. Enter the Bucket Name exactly as created in Step 1.
4. Select the Region that matches the region you chose when creating the bucket.
5. Click Test Connection to verify the credentials and bucket access.
6. Once the test passes, click Save Settings.

Tip

If the test connection fails, double-check that the region in WPsigner matches the region you selected in the Wasabi console. A mismatch is the most common configuration error.

---

Use Cases

Use Case	Description
Long-term archival	Store signed contracts and agreements for years at a flat, predictable cost with no surprise egress fees.
Regulatory compliance	Keep tamper-proof copies of signed documents outside your WordPress server to meet audit and retention requirements.
Disaster recovery	Maintain an off-site backup of all signed PDFs in case of server failure or data loss.
High-volume operations	Organizations that process hundreds of documents per month benefit from Wasabi’s low per-TB pricing.
Multi-site backup	Centralize signed document storage from multiple WordPress installations into a single Wasabi bucket.

---

Wasabi vs Amazon S3

Feature	Wasabi	Amazon S3
Egress Fees	None	$0.09/GB
Storage Cost	$6.99/TB/mo	$23/TB/mo
API	S3-compatible	Native S3
Regions	13	21+
Min Storage	1 TB	None

---

Security

Same security as Amazon S3: AWS Signature V4, AES-256-GCM encryption, rate limiting, nonce verification.

---

Troubleshooting

Problem	Cause	Solution
Test connection fails with “InvalidAccessKeyId”	The access key is incorrect or has been deactivated.	Verify the access key in the Wasabi console under Access Keys. Generate a new pair if needed.
Test connection fails with “SignatureDoesNotMatch”	The secret key is incorrect or contains trailing whitespace.	Re-paste the secret key, making sure there are no extra spaces before or after it.
”NoSuchBucket” error	The bucket name in WPsigner does not match an existing bucket.	Check the exact bucket name in the Wasabi console and re-enter it in WPsigner.
”Region mismatch” or “PermanentRedirect”	The region selected in WPsigner does not match the bucket’s actual region.	Open the bucket properties in Wasabi to confirm the region, then update the WPsigner setting to match.
Uploads succeed but files are empty (0 bytes)	Server memory or execution time limits are too low to process large PDFs.	Increase memory_limit to at least 256M and max_execution_time to 120 in your php.ini.
Intermittent timeout errors	Network instability or high latency between your server and the Wasabi region.	Choose a Wasabi region geographically closer to your hosting server, or increase the WPsigner timeout value.

---

Compatibility

Component	Minimum Version	Recommended
WPsigner	2.1.0	Latest
WordPress	5.8	6.4+
PHP	7.4	8.1+
cURL extension	Required	Latest
OpenSSL extension	Required	Latest

---

Next Steps

• Amazon S3 — Native AWS storage with the broadest region coverage.
• Cloudflare R2 — Zero egress fees with a built-in global CDN.
• Google Drive — Sync signed documents to your Google Workspace.
• Dropbox — Automatic backups to your Dropbox account.