MinIO: object storage with an S3-compatible API
Use MinIO object storage for files such as images and videos. Check API compatibility, storage limits, and performance for your application and deployment.
MinIO deployment considerations
S3-compatible object storage, a web console and resource allocation within a fixed monthly zone package.
S3 API compatibility
MinIO supports the S3 API, but compatibility can vary by operation, SDK, and client. Test your application against the configured endpoint.
Modern web management console
Use the MinIO web console to manage buckets, upload and download files, and configure access policies. Console language options depend on the version.
Object storage and persistent volumes
MinIO stores objects separately from an application’s local files. Storage isolation and performance depend on the deployment and package.
Storage planning within fixed package limits
Storage and network transfer count toward the selected monthly package limits. Availability of resource changes depends on the service configuration.
Frequently asked questions about MinIO
Answers to common questions about MinIO, the S3 API, and object storage:
MinIO and cloud object storage
Object storage can keep application files separate from an application’s local filesystem. MinIO is an open-source object-storage server with an S3-compatible API. Supported features and performance depend on the software version and deployment.
What is MinIO, and what does S3 API compatibility mean?
MinIO is an open-source object-storage server that exposes an S3-compatible API. It stores objects and metadata in buckets and makes them available through configured endpoints.
S3 API compatibility can help applications use MinIO with existing SDKs, but support varies by operation and client. Test your integration and configure credentials and endpoints for your deployment. Cloud containers Object-storage services can be configured as backup destinations, subject to the source application and backup policy. Cloud database Configure and test backup policies separately; MinIO does not by itself create application backups.
MinIO setup and deployment options
Self-hosting MinIO involves configuring network access, console and API endpoints, TLS, service startup, storage, and backups. Requirements depend on your deployment and operational setup.
Container-based MinIO deployment options depend on the available service configuration. Review how API and console access, persistent storage, domains, and TLS are handled before deployment. International service creation is currently paused.
MinIO, FTP hosting, and other object-storage services
Compare storage options by API support, access controls, storage model, network requirements, pricing, and operations.
| Feature | MinIO on Deplomo Cloud | FTP-based file hosting | Other object-storage services |
|---|---|---|---|
| Storage architecture and API | Object storage with an S3-compatible API; check supported operations | FTP-based file transfer; API support depends on the service | S3 API support varies by provider and implementation |
| Transfer speed and latency | Depends on deployment location, network path, and workload | Depends on provider, network path, and service configuration | Transfer performance and access depend on the provider and region |
| Data location and access controls | Data access and ownership depend on account and deployment configuration | FTP credentials and access controls depend on the service configuration | Data location depends on provider, region, and configuration |
| Bucket management tools | MinIO provides a web console for managing storage, depending on version and configuration | File managers and transfer tools vary by host and setup | Console workflows vary by provider and configuration |
| Pricing and billing | Fixed monthly EUR package pricing | Pricing and billing terms depend on the provider and package | Storage, transfer, and other charges vary by provider and usage terms |
MinIO is one object-storage option. Review its S3 API compatibility, storage limits, network access, and operational requirements for your use case.
Planning a MinIO deployment
Review the deployment configuration and service status before planning these steps:
- Choose Directus from the marketplace When MinIO service creation is available, select a compatible MinIO image.
- Plan storage and resources: Estimate storage capacity from your expected objects and retention needs, and select resources within the package limits.
- Configure access: After deployment, use the service endpoint and credentials provided by the configuration. Store secrets securely and restrict access.
- Create a bucket and configure credentials: Create a bucket, generate access credentials, and configure them in your application or backup tool. Avoid embedding secrets in client-side code.
MinIO setup, storage, and operations
MinIO provides an object-storage option with an S3-compatible API. Data availability, security, performance, and capacity depend on deployment settings, resource limits, and your backup and recovery practices.
Review MinIO’s supported features, package limits, and current service availability.
Run MinIO in seconds
Automatic installation, instant setup and custom domain support with a free security certificate.