Connect your existing object storage
Use a storage service that implements the S3 API and supports path-style bucket addressing. Its HTTPS endpoint must be reachable from the public internet.
Integration
S3-compatible Storage integrations on Wodby
Use S3-compatible Storage for Wodby backups on object storage such as MinIO or Ceph. Connect a public HTTPS endpoint, an access key pair, and an optional region, then select the backup bucket.
Storage
Limit access to backup buckets
Use a key scoped to the buckets Wodby may read and write. Enable bucket listing for the picker, or enter an exact bucket name.
Supported workflows
How S3-compatible Storage fits into Wodby
Each supported integration kind maps S3-compatible Storage into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider configuration into workloads.
Storage
Object Storage
Send backup archives to S3-compatible object storage such as MinIO or Ceph through a public HTTPS endpoint.
- Enter an HTTPS endpoint without a bucket name or path. Private or internal addresses are not accepted.
- Use a service that supports path-style addressing and supply its expected region; the default is us-east-1.
- Provide an access key pair with bucket-checking, object read and write, and multipart-abort permissions. Bucket listing is optional.
Configuration surfaced to workloads
Endpoint URLRegionAccess Key IDSecret Access Key
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to S3-compatible Storage.
Stack fit
Stacks that commonly pair with S3-compatible Storage
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
PostgreSQL
Stack
Self-hosted PostgreSQL database stack for applications that want a managed Postgres service inside the same delivery workflow.
PostgreSQL is a representative stateful stack when backup archives should land in external object storage.
View stackMariaDB
Stack
Self-hosted MariaDB database stack for applications that want a managed relational database inside the Wodby workflow.
MariaDB stacks benefit from off-platform backup targets managed through a storage integration.
View stackWordPress
Stack
WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.
WordPress projects commonly want external backup storage for stateful production environments.
View stackDrupal 11
Stack
Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.
Drupal sites benefit from backup workflows that push archives outside the running environment.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.