Use S3 clients without sending data to an AWS region
S3 compatibility separates the client interface from the infrastructure behind it. Configure an AWS SDK, CLI profile, or application with the Predastore endpoint and local credentials; the requests are authenticated and served by your Spinifex deployment. Applications can keep familiar bucket and object workflows while the data remains on operator-controlled infrastructure.
Predastore supports AWS Signature Version 4 authentication and multipart uploads. Its distributed backend uses Reed–Solomon erasure coding to divide objects into data and parity shards across storage nodes. A filesystem backend is also available for compact, single-node deployments.
Where Predastore fits
Application objects
Give software an S3-compatible endpoint for artifacts, datasets, media, logs, and other object-shaped data.
Spinifex images
Store machine images and other assets used by the wider Spinifex compute and storage stack.
Edge data
Keep object access beside the workload when latency, bandwidth, policy, or disconnection rules out a remote region.
Evaluate S3 compatibility against real operations
“S3 compatible” is not a single binary certification. Products implement different portions of a large API, and applications rely on different details. Test the operations, headers, authentication flows, object sizes, and failure behaviour your workload needs rather than relying on the label alone.
Client path
Test the exact SDK version, CLI commands, Terraform provider, or application library used in production.
Object path
Exercise create, read, list, delete, and multipart operations with representative object names and sizes.
Identity path
Verify SigV4 credentials and the IAM policies needed by each application or operator.
Failure path
Measure the deployment under the node, disk, and network failures its topology is intended to tolerate.
Operations path
Plan capacity, monitoring, backups, upgrades, repair, and recovery as part of the storage design.
Object storage as part of a complete edge cloud
Predastore is included with Spinifex rather than presented as an isolated hosted storage service. The same deployment can expose EC2-compatible compute, EBS-compatible block storage, S3-compatible object storage, VPC networking, and IAM identity. That is useful when an application needs several AWS-style primitives in the same on-premise or edge environment.
Start with the Spinifex architecture and FAQ, then use a sandbox to run the object operations your application depends on before choosing a production storage topology.