Your S3 storage.
No servers
to buy.

Upload (PUT), read (GET), inspect metadata (HEAD), list and delete: we test the operations used by your S3 client, pagination and error responses. For large files, multipart upload transfers parts concurrently and lets a failed part be retried. Support and settings are validated with your software.

Acceptance: upload, read-back, integrity checking and recovery after interruption. Dependencies on other AWS services are identified separately.

Throughput depends on network capacity, object sizes and concurrent transfers. A million small files behaves differently from a few multi-gigabyte videos. We define a representative dataset and run tests from your environment.

Measure: effective read/write throughput, requests per second, p95 latency and the time required to restore priority data.

Versioning retains multiple states of an object. Object Lock aims to prevent deletion of a protected version for a defined period. Depending on the mode, bypass permissions may exist: versioned does not mean immutable. We check availability, retention modes and configuration before including this protection in your architecture.

Acceptance: attempted deletion using the agreed roles, version recovery and retention expiry checks. RPO defines tolerable data loss; RTO defines the target recovery time.

We scope access per application and separate write, read and administrative permissions where needed. HTTPS connections, secret storage and key rotation form part of the configuration. Encryption at rest or client-side, key management and access logs are scoped with your security team.

Acceptance: permitted access, denied access, key revocation and the agreed audit evidence. Available mechanisms are documented in the service scope.

Durability concerns the risk of losing an object; availability concerns being able to access it. Replication and erasure coding are different protection mechanisms; distribution across disks does not demonstrate replication across sites. We clarify failure domains, recovery scenarios and appropriate commitments with you.

Contract scope: agreed architecture, SLA, support, recovery responsibilities and exclusions. The HDS and ISO 27001 certifications cited apply to the data centre.

Capacity planning includes retained versions, growth and, depending on service behaviour, unfinished multipart uploads. We define retention and deletion rules, then validate the required functions. Migration combines an initial transfer with delta synchronisation and checks on objects, metadata and versions in scope.

Acceptance: reconciled inventory, verified integrity and an export read back using your software. Mintera charges no egress fees; costs from the source provider, network and professional services must still be assessed.