The Object Storage Server
An S3 endpoint on a machine you own, with your buckets, your access keys, and every bucket proved working before we hand it over.
Something in your stack wants an S3 bucket. A backup tool, an application, an archive somebody says you have to keep for seven years. The usual answer is an account with a storage provider who bills by the byte and holds your data on their terms.
We put the store on a machine you already have, so the bytes stay on your hardware and the bill stops growing with them. You get an endpoint on your own hostname over HTTPS, buckets with hard capacity limits, and access keys we generate on your machine and hand to a person you name.
Before we finish we write an object into every bucket, read it back and compare it byte for byte, push a large one through as a multipart upload, and try each key against a bucket it was never granted. Then we tell you in one sentence what one server survives, because a single machine is a single machine and you should hear that from us rather than from a dead disk.
What's included
An S3 endpoint on your own hostname over HTTPS with your certificate, and the store's internal parts shut away so only that endpoint answers from outside the machine
Up to five buckets with hard capacity limits that stop writes rather than filling your disk, plus rules that clear out abandoned uploads and expire old versions on the schedule you choose
Up to five access keys, each scoped to the buckets you name and read-only wherever you want it that way, generated on your machine and handed to a person you name. We keep no copy of any of them
Every bucket proved before handover: an object written, read back and compared byte for byte, a large one uploaded in parts, a time-limited link tested to expiry, and each key tried against a bucket it should not reach
Optional version history, so a file somebody overwrote or deleted last Tuesday can be pulled back, and a write-once period on one bucket where you need it
One copy of a chosen bucket sent off the machine on a schedule, with an object pulled back out of that copy and checked, where you want one
A handover carrying the exact settings for your S3 client, the arithmetic behind every capacity figure, and a plain sentence about what your storage layout survives
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
SSH access with sudo or root to the machine, with no other object store already running on it
The mounted filesystem the objects will live on, on storage attached to that machine
The hostname your applications will connect to, already pointing at the server, with a TLS certificate, key and chain for it
Your buckets (up to five) with the capacity each needs, and your access keys (up to five) with what each may reach
The person who will receive the access keys, and how we should send them
A maintenance window for the reboot test
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The File Storage Server
Your company files on a server you own, for up to twenty-five people, with no per-seat bill and nobody else holding a copy. Before anything moves, we read the file share you have now and hand you a list of every file that will not survive the trip.
The Proxmox Backup Server Setup
Proxmox Backup Server standing behind every guest on your node or cluster, with one of your machines restored from its backup, booted in front of you and timed before we hand anything over.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.
The Reverse Proxy Setup
A hardened front door for up to three applications you already run — HTTPS ends at the proxy, scanner probes are turned away, and traffic is balanced across your backends while the apps behind it stay exactly as they are.