Build and operate your own branded S3 service
Combine private scale-out object storage with customer provisioning, enforced capacity quotas, storage and traffic accounting, billing exports, data protection and a customisable end-user S3 File Manager.
One operating model from onboarding to accounting export
A commercial S3 service needs more than an endpoint. It needs clear customer boundaries, measurable consumption, controlled credentials and an experience that carries the provider’s identity.
Onboard
Create the customer record, dedicated S3 identity, bucket, hard capacity quota and credentials.
Deliver
Provide S3 API access, AWS CLI compatibility and the branded end-user S3 File Manager.
Measure
Collect storage snapshots and upload/download traffic with visible coverage status.
Export and expand
Export calculated usage for downstream invoicing and grow the cluster as demand increases.
Not every euroNAS S3 implementation targets the same service model
| Capability | euroNAS Premium | euroNAS HA Cluster | eEKAS |
|---|---|---|---|
| Architecture | Single-server Storage OS | High-availability storage pair | Distributed Ceph scale-out cluster |
| Bucket-count quota | Included | Included | Included |
| Enforced capacity quota | — | — | Included |
| S3 File Manager | Included | Included | Included and customisable for the provider |
| Storage and traffic billing workflow | — | — | Included |
| Commercial multi-customer service | Not recommended | Not recommended | Recommended |
Turn collected consumption into reviewable, exportable charges
The eEKAS workflow separates capacity control from measured consumption and makes the quality of traffic coverage visible before a period is closed.
Hard capacity quota
Writes that would exceed the customer’s configured Ceph bucket quota are rejected.
Storage peak
Billable storage uses the highest collected bucket usage in the selected period—not the quota and not simply the latest value.
Upload and download
Optional traffic charges use S3 request and response byte counters from the gateway service.
Coverage status
Complete, provisional, partial or incomplete status helps operators judge whether recent traffic figures are ready for review.
Review the evidence before sending data downstream
Keep end-user access separate from storage administration
Administrative service console
Create customers, issue credentials, define quotas and prices, configure protection, monitor coverage and export usage.
Customisable S3 File Manager
A separate browser application with its own login. Customers can manage permitted buckets and objects, upload files and work with versions without access to the admin console.
Package capacity, retention and recovery as understandable service tiers
S3 replication and disaster recovery
Compare a read-only standby site, asynchronous active-active operation, an external current-object mirror and checkpoint-based backup and archive.
SMB access with S3 WORM
Offer familiar SMB file access while protected files are stored directly as S3 objects with COMPLIANCE retention.
Design for normal operation and recovery
Networks
Redundant client and cluster networks plus enough WAN capacity for initial sync and catch-up.
Gateways
Load-balanced S3 endpoints, protected credentials and monitored usage logging.
Capacity
Headroom for customer growth, retained versions, recovery and cluster rebalancing.
Recovery
Documented promotion, restore, application routing and return-to-service procedures.
Define the service before building the cluster
Customer count, object growth, pricing, traffic, retention, brand, site topology and recovery commitments shape the right architecture.