S3-compatible object storage has become the default interface for storing unstructured data. The API is well-understood, client libraries exist for every language, and most applications already know how to talk to it. The question is not whether to use the S3 API, but where to run the storage that implements it.
The cost structure of public cloud object storage ¶
Public cloud object storage pricing has three components: storage capacity, API request count, and egress bandwidth. The first two are predictable. The third is not, because egress charges apply every time data leaves the cloud provider's network, including when it moves to a different region operated by the same provider. For applications that read large objects frequently, egress costs can exceed storage costs within a few months.
Private S3-compatible storage: what changes ¶
On private infrastructure, egress within the facility is free. Data moving between your compute nodes and your storage nodes over a private VLAN does not incur a per-GB charge. The cost model becomes simpler: you pay for the storage hardware and the uplink, and that is it. For workloads with high read rates or large object sizes, this is materially cheaper than public cloud storage at scale.
Encryption and key management ¶
On the Husk Mesh Vault storage layer, AES-256 encryption is applied at rest and TLS 1.3 is used in transit. The encryption keys are managed in your control plane, not in a key management service operated by the storage provider. This means that if you terminate your contract and export your data, the keys leave with you. There is no residual access to your data after the contract ends.
Practical migration from public cloud storage ¶
Migrating an existing S3 bucket to private infrastructure is straightforward if the application uses the S3 API without provider-specific extensions. The main work is updating the endpoint URL and credentials, then transferring the existing objects. For buckets larger than a few terabytes, a parallel transfer tool reduces the migration window significantly. The Husk Mesh Vault Migration Assistance engagement includes data transfer tooling and a post-migration validation checklist.
Private S3-compatible storage is not a replacement for public cloud storage in every situation. For workloads with high egress rates, regulated data, or strict key management requirements, it is worth the operational overhead of running your own nodes.