OptimiDoc Server Help Center
OptimiDoc Server Help Center
Breadcrumbs

S3-Wasabi Destination

The S3-Wasabi destination stores scanned documents in S3-compatible cloud object storage such as Wasabi, Amazon S3, or MinIO -- scalable, cost-effective long-term storage with high durability.

How It Works

The S3-Wasabi destination is a delivery-only destination. OptimiDoc authenticates to the storage service with an Access Key and Secret Key and writes each output document as an object into the configured Bucket, under the optional Path prefix. The destination speaks the S3 API, so it works with any S3-compatible service -- it is optimised for Wasabi Hot Cloud Storage but also supports Amazon S3, MinIO, and similar providers. The bucket must already exist; OptimiDoc does not create buckets.

Configuration Fields

Field

Description

Access Key

Access key ID for API authentication (from the provider's console, e.g. AWS IAM or the Wasabi console).

Secret Key

Secret access key paired with the access key ID. Keep it confidential.

Bucket Name

Name of the existing S3 bucket where objects are stored.

Region

Storage region of the bucket (e.g. us-east-1, eu-central-1).

Path

Optional key prefix (folder path) within the bucket, e.g. scans/ or department/invoices/.

The Path prefix and the output filename both support placeholders resolved at scan time -- see Output Options. The final object key is {Path}{filename}.{extension}; for example Path scans/{user}/ with filename {date}_{counter} yields scans/jsmith/2024-01-15_00001.pdf.

Provider-Specific Configuration

Wasabi

Setting

Value

Region endpoint

s3.{region}.wasabisys.com (handled automatically)

Common regions

eu-central-1 (Amsterdam), us-east-1 (Virginia), us-west-1 (Oregon), ap-northeast-1 (Tokyo)

Credentials

Create access keys in the Wasabi console under Access Keys

Amazon S3

Setting

Value

Region endpoint

s3.{region}.amazonaws.com (handled automatically)

Common regions

eu-west-1 (Ireland), us-east-1 (N. Virginia), eu-central-1 (Frankfurt)

Credentials

Create an IAM user with programmatic access and an S3 policy granting s3:PutObject / s3:GetObject

MinIO (Self-Hosted)

Setting

Value

Region

As configured in your MinIO deployment

Credentials

Use the MinIO access key and secret key from the MinIO console

Minimal IAM Policy (AWS) 

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:PutObject", "s3:GetObject", "s3:ListBucket"],
      "Resource": [
        "arn:aws:s3:::your-bucket-name",
        "arn:aws:s3:::your-bucket-name/*"
      ]
    }
  ]
}

For Wasabi, an equivalent policy can be created in the Wasabi console under Policies.

Storage Considerations

Factor

Recommendation

Bucket creation

Create the bucket before configuring the destination -- OptimiDoc does not create buckets

Versioning

Enable bucket versioning for audit trails and accidental-overwrite protection

Lifecycle rules

Transition old scans to cheaper tiers or auto-delete after a retention period

Encryption

Enable server-side encryption (SSE-S3 or SSE-KMS) for data at rest

Troubleshooting

Issue

Possible Cause

Resolution

Access denied

Invalid access key or secret key

Verify the credentials in the provider console

Bucket not found

Incorrect bucket name or region

Ensure the bucket exists in the specified region

Signature mismatch

Region mismatch

Verify the Region matches the bucket's actual region

Connection timeout

Network or firewall issue

Ensure the OptimiDoc server can reach the S3 endpoint on port 443