Store files and backups
Order Object Storage, upload files in the dashboard and with an S3 client, and keep snapshots of a server, from start to finish.
In the dashboard
This tutorial gives your files a home in Object Storage and keeps copies of a server that you can restore. You order Object Storage with a first bucket, upload a file in the dashboard, connect the AWS CLI with an access key to upload a whole folder, and take a snapshot of a server. Each section ends with something you can check before you go on.
Object Storage costs the plan you choose. Each plan includes an allowance of storage and names the rate for storage above it (How Object Storage is billed). Snapshots use the snapshot storage that each server plan includes, and more storage is a service of its own (How snapshots are billed). If buckets and snapshots are new to you, read Object storage compared with a disk and How backups and snapshots protect your data first.
Before you begin
Section titled Before you begin- A Coritan account. Create an account if you have none, then sign in.
- Credit for the first invoice, or a card or PayPal to pay it when you order (Add credit to your balance).
- For section 3, a recent AWS CLI on your computer, and outgoing HTTPS allowed on TCP port
7337. - For section 4, a Container Apps server. Run an app or a database orders one.
1. Order Object Storage
Section titled 1. Order Object Storage- In the dashboard, go to Object Storage and select Order Object Storage.
- Under Plan, choose a plan, and the billing cycle with the buttons beside the Plan heading.
- Under Region, choose the region closest to the machines and people that use the files. Each bucket answers only at its own region's endpoint.
- Under First bucket, type
backupsin Bucket name. Coritan puts your account's prefix in front, and the hint shows the full name, such asWe create it as u7-backups. - Check the summary under Your order, then select the button under it. It reads Place order when your credit pays for it, and Place order and pay when you pay on the next page.
- If the order's page reads Order placed, payment due, pay under Pay invoice.
The order's page title becomes Your order is ready once the service is active. Reload the Object Storage page, and the service shows the status active (Order Object Storage).
2. Upload a file in the dashboard
Section titled 2. Upload a file in the dashboard- Open the service from the Object Storage page and select the Buckets tab.
- Select the bucket's name, such as
u7-backups, to open its object browser. - Select Upload… and choose a file, or drag it from your computer onto the list.
The Transfers panel at the bottom right follows the upload, and the file appears in the list with its Size. Select its name to download it again (Upload, download and delete objects).
3. Connect the AWS CLI
Section titled 3. Connect the AWS CLIThe dashboard uploads one file at a time. An S3 client such as the AWS CLI uploads whole folders, and your scripts can use it for backups.
On the service's Access keys tab, select Create key….
In Label, type where you use the key, such as
laptop. Under Permissions, choose Read and write. Under Scope, choose the bucketu7-backups.Select Create key.
Under Save the secret key now, the dialog shows two blocks for a profile called
coritan. Paste the first into~/.aws/credentialsand the second into~/.aws/configon your computer.Store the secret key in a password manager, then select I have saved it. The dashboard never shows it again.
Wait a couple of minutes for the key to reach storage, then upload a folder and list the bucket:
Shellaws --profile coritan s3 sync ./site/ s3://u7-backups/site/ aws --profile coritan s3 ls s3://u7-backups/site/
The list shows the files from your folder, and the object browser shows them in a site folder (Create and revoke access keys, Connect an S3 client).
4. Take a snapshot of a server
Section titled 4. Take a snapshot of a serverA snapshot is an archive of a server's files. It belongs to your account, so it stays after the server is gone, and you can restore it onto any of your servers.
- In the dashboard, go to Container Apps, open the server and select the Snapshots tab.
- Select Take snapshot…. The dialog shows the server's disk usage against what is left of your allowance, under Estimated size against what is left.
- Keep the suggested Name, such as
snapshot-2026-09-25-1430, or type your own. - Tick Lock this snapshot to keep it from being deleted by accident.
- Select Take snapshot.
The snapshot appears on the server's Snapshots tab and on the account's Snapshots page, with a Locked badge. Select Ready on that page to see only the snapshots you can restore (Take a server snapshot).
A snapshot holds the server's files only. It leaves out the databases on the server's Databases tab, so export those with a MySQL client. A Cloud Compute instance keeps its snapshots and backups on its own tabs (Back up and restore an instance).
Troubleshooting
Section titled TroubleshootingInvalidAccessKeyId- The key has not reached storage yet. Wait a couple of minutes, then try again.
NoSuchBucket- The client sent the request to another region's endpoint. Use the endpoint the key's dialog gave, which ends in
:7337(Connect an S3 client). - Not enough snapshot storage
- The snapshot would not fit what is left of your allowance. Delete an old snapshot, or select Order more storage (Order more snapshot storage).
Next steps
Section titled Next steps- Restore a snapshot onto a server
- Schedule server tasks, to take snapshots on a timetable
- Share a file with a presigned URL