Object storage (S3)
S3-compatible object storage in WebShield — buckets, access keys, pricing, and client configuration.
WebShield object storage is S3-compatible, built for backups, media, logs, and application data. Any S3 client works: aws CLI, rclone, s3cmd, and the AWS SDKs.
- Endpoint:
https://s3.webshield.pro. Use either path-style (https://s3.webshield.pro/<bucket>/<key>) or virtual-hosted addressing (https://<bucket>.s3.webshield.pro/<key>). - Billing: pay for what you actually store and serve. Stored volume — per GB per month; outbound traffic — beyond the free allowance. Debited from the balance once a month. Current prices are on the service page.
Enabling the service
Section titled “Enabling the service”- Open S3 storage in the control panel (account level).
- Click Enable storage. The first key appears, with full access to all buckets.
- Save the Secret Access Key immediately: it is shown once, when the key is issued.
Access keys
Section titled “Access keys”Expand S3 connection and access keys below the bucket list to find the server address and access keys. This section opens automatically when you first enable storage. Click New key to open a dialog with its name, permissions, buckets and expiry date. Existing keys appear as table rows. You do not need a separate key to manage files in the browser.
One key for everything is convenient until it leaks. Give each application its own key: server backup, website, CI. If the website key leaks, the backups stay out of reach.
A key has one of three permission levels:
| Permissions | What it can do |
|---|---|
| Read | download and list files |
| Read and write | also upload, delete and tag; sets retention on write, but cannot lift Object Lock protection |
| Full access | everything, including bypassing GOVERNANCE and removing legal holds |
- A key covers selected buckets or all of them, including future ones. Deleting all selected buckets does not give a limited key access to other buckets.
- An expiry date is optional; after it the key switches off by itself.
- A key’s permissions and buckets never change. Need different ones — issue a new key, move the application to it and delete the old one. Routine key rotation works the same way.
- A new key starts working, and a deleted one stops, within about a minute.
- Up to 20 keys per account.
To create and delete buckets from an S3 client, issue a new key with Full access, select All buckets, including future ones, and enable Create and delete buckets over S3. New buckets are private. S3 deletion requires an empty bucket, including old versions and delete markers. See the rclone setup.
Buckets
Section titled “Buckets”Click Create bucket, then enter a name and choose a region in the dialog. Once created, the new bucket opens its file manager.
- Names are unique across all WebShield accounts and regions.
- Buckets are available right after sign-up, with no prepayment: on the first bucket the panel asks you to accept pay-as-you-go billing. Until the first payment, limits apply: up to two buckets of 10 GB and 50 GB of public bucket traffic a month (beyond that, anonymous reads close until the month ends). A full bucket turns read-only, and files cannot be deleted from it either. A top-up of any amount lifts the limits.
- When creating a bucket you choose its region:
ru-1(Russia) oreu-1(Europe). The region determines where the data is durably stored; the region is set at creation and cannot be changed later. The endpoint is the same for all regions. - A bucket is private by default. A public bucket allows anonymous downloads by direct URL (
https://s3.webshield.pro/<bucket>/<key>) — for example, to serve images or files on a website; listing the bucket contents stays private. Access can be changed with the Public checkbox in Bucket settings; the change takes effect within about a minute. - The Files button next to a bucket opens the built-in file manager: browse folders (contents load lazily as you expand them), upload small files, download and delete objects. For bulk transfers and large objects use an S3 client.
- The checkbox in the file header selects loaded rows. Selecting a folder includes all its contents, even when collapsed; select additional pages separately. The trash icon on the right of the header deletes the selection and becomes available when objects are selected.
- Uploads show progress and a cancel button; after the transfer, wait for the server to save the files. Some files may have been saved after cancellation or an error — check the list before trying again.
- Use 3–63 lowercase Latin letters, digits and hyphens, starting and ending with a letter or digit. Dots and reserved names are unavailable. Deleted names are not yet reissued.
- Create and delete buckets in the control panel or with an S3 key that has bucket management permission. Deleting a non-empty bucket in the control panel requires confirmation and irreversibly removes all objects.
Versioning and Object Lock
Section titled “Versioning and Object Lock”- Versioning is enabled with a checkbox in Bucket settings: every overwrite keeps the previous version of the object, and a delete puts a delete marker instead of erasing data. Versions are available through standard S3 calls (
list-object-versions,get-object --version-id; restore by copying the desired version over the current one). - Deletion protection — a lock term for the bucket’s files, see below.
- Object Lock (WORM) is enabled with a checkbox in Bucket settings and locks nothing by itself: the term comes from deletion protection or an S3 client (
put-object-retention). A full-access key can bypassGOVERNANCEmode, so onlyCOMPLIANCEprotects against such a key being stolen. Object Lock works on object versions, so it enables versioning too. - Both settings are irreversible (as in AWS S3): versioning and Object Lock cannot be turned off once enabled.
- Old versions occupy billed storage just like regular objects. Without deletion protection, old versions aren’t cleaned up automatically — delete unneeded ones with an S3 client (
delete-object --version-id). - Versions, like regular objects, are kept in the region storage alongside current data.
Deletion protection
Section titled “Deletion protection”The term — 7, 14, 30 or 90 days — is picked in Bucket settings → Deletion protection. Restoring deleted files and deleting the bucket are also available there.
- Every file written to the bucket is locked by the storage for that term. A delete request only hides the file and an overwrite creates a new version — the previous data stays.
- Files already in the bucket are locked by the first pass right after protection is turned on.
- The storage extends the lock of files that haven’t been deleted, every half term.
- Deleted and overwritten data is kept until the term ends and then removed automatically, once a day. While it’s kept, it takes up billable space.
- Restore deleted undeletes files deleted after a given moment, as long as their term hasn’t run out. If a key was stolen, delete it first.
- The term can’t be shortened for files already written: a new term or turning protection off applies to new files, existing locks run their course. While they last, the bucket can’t be deleted.
- Turning protection on enables versioning and Object Lock, which can’t be turned off later.
Object Lock without deletion protection locks nothing. A regular delete keeps the previous
version, but deleting a specific version (aws s3api delete-object --version-id, rclone with
--s3-versions) erases it immediately and for good. Old versions aren’t cleaned up either.
A backup example is in the restic guide.
Pricing and limits
Section titled “Pricing and limits”Stored volume and S3 charges for the current month appear above the bucket list. Expand Usage and cost for traffic and rates. Follow Balance and billing for all services in that section to see the account balance, which includes all services and payments.
- Storage is billed per GB·month based on the average daily volume: 1/N of the monthly price accrues each day (N — days in the month).
- Outbound traffic is free up to three times the monthly average stored volume (store 100 GB — serve 300 GB per month for free); beyond the allowance it is billed per GB. Inbound traffic and operations (GET, HEAD, LIST, PUT, POST, etc.) are not billed and not limited in number.
- Charges show up in the panel every day, but we debit the balance once a month — when the calendar month ends.
- If the balance goes negative after the monthly charge, access is not cut off immediately: we send a notification asking you to pay. If the debt stays unpaid for 7 days, the storage switches to read-only: downloads keep working, uploads are rejected, and no data is deleted. Full access is restored automatically after payment.
- A single
PUTis limited to 5 GB; upload larger objects with multipart upload (S3 clients do this automatically).
Media delivery and caching
Section titled “Media delivery and caching”- Objects in public buckets are served through the WebShield edge node closest to the visitor and are cached on it: repeated downloads and Range requests (video seeking) are served locally, without a round trip to the storage.
- After overwriting an object under the same name, the old version may be served from the cache for up to 1 hour. For an instant switch, upload the file under a new name (for example, with a version in the name:
logo-v2.png). - The
Cache-Controlheader set at upload time is honored by both the edge cache and browsers: set a longmax-agefor immutable files. - Signed requests (S3 clients with keys, presigned URLs) are never cached and always go straight to the storage.
- Turning off bucket public access stops the delivery (including cached objects) within a minute or two.
Connecting a client
Section titled “Connecting a client”Any S3-compatible client works with the WebShield endpoint. Step-by-step setup guides:
- AWS CLI — the official command-line client.
- rclone — sync and mirror directories.
- s3cmd — a lightweight command-line client.
- SDKs — boto3 (Python), JavaScript, Go, PHP.
Nightly backups of a computer, server and 1C databases — see the restic guide.
In every client you need the endpoint https://s3.webshield.pro, the access key pair from the control panel, and the full bucket name.