Loading…
Loading documentation...
Link S3-compatible object storage in your Servers Are Up environment, upload objects with AWS CLI or rclone and generate presigned URLs.
Commands checked on 2026-11-12 with AWS CLI v2.18, rclone 1.68, Node.js 24, sau CLI 0.2.0.
Your application and servers will store and serve objects from a private S3-compatible bucket managed in Storage > Storage (/dashboard/storage), uploading files over TLS, enforcing private-by-default bucket ACLs, and issuing short-lived presigned GET and PUT URLs so browsers upload and download directly without proxying large files through your Node.js server.
/dashboard./dashboard/storage and /products): Connect Amazon S3, Cloudflare R2, DigitalOcean Spaces, Backblaze B2, Wasabi, Hetzner/Linode/Vultr Object Storage, or check live catalog availability on /products (GET /api/v1/catalog?type=STORAGE). Note that on catalog S3 plans where monthly read transfer reaches its included cap, reading objects pauses until the 1st of the month while uploads keep working./cloud-storage and /dashboard/blob-storage): If you want turnkey 250 GiB–25 TiB plans ($9/mo–$399/mo plus a 5 GiB free developer tier) hosted via Microsoft Azure with double encryption and WORM locks, follow Purchase Azure-backed cloud storage with WORM locks and SAS.aws CLI v2 or rclone installed locally or on your Linux VPS./dashboard/storage) and select the Buckets / Object Storage view.Access Key ID, and Secret Access Key) and create or register a private bucket such as prod-media-assets.rcloneConfigure a named sau-s3 profile on your workstation or CI runner so credentials never appear in shell arguments (ps aux):
aws configure set aws_access_key_id "YOUR_SCOPED_ACCESS_KEY" --profile sau-s3
aws configure set aws_secret_access_key "YOUR_SCOPED_SECRET_KEY" --profile sau-s3
aws configure set region "us-east-1" --profile sau-s3
Upload a test artifact with explicit Content-Type and Cache-Control metadata and list the bucket contents:
echo '{"hello":"servers-are-up"}' > sample-manifest.json
aws --profile sau-s3 --endpoint-url https://s3.example-storage.com \
s3 cp sample-manifest.json s3://prod-media-assets/releases/sample-manifest.json \
--content-type "application/json" \
--cache-control "private, max-age=300"
aws --profile sau-s3 --endpoint-url https://s3.example-storage.com \
s3 ls s3://prod-media-assets/releases/
To share a private file for 15 minutes (900 seconds) from the terminal:
aws --profile sau-s3 --endpoint-url https://s3.example-storage.com \
s3 presign s3://prod-media-assets/releases/sample-manifest.json \
--expires-in 900
In a Next.js or Node.js backend, use @aws-sdk/client-s3 and @aws-sdk/s3-request-presigner to mint 5-minute upload (PutObjectCommand) and download (GetObjectCommand) URLs after checking that the signed-in user owns the tenant prefix:
import { S3Client, PutObjectCommand, GetObjectCommand } from '@aws-sdk/client-s3';
import { getSignedUrl } from '@aws-sdk/s3-request-presigner';
const s3 = new S3Client({
region: process.env.S3_REGION ?? 'auto',
endpoint: process.env.S3_ENDPOINT!,
credentials: {
accessKeyId: process.env.S3_ACCESS_KEY_ID!,
secretAccessKey: process.env.S3_SECRET_ACCESS_KEY!,
},
});
export async function createTenantUploadUrl(tenantId: string, fileId: string, mimeType: string) {
const key = `tenants/${tenantId}/uploads/${fileId}`;
const command = new PutObjectCommand({
Bucket: process.env.S3_BUCKET!,
Key: key,
ContentType: mimeType,
});
return { key, uploadUrl: await getSignedUrl(s3, command, { expiresIn: 300 }) };
}
export async function createTenantDownloadUrl(key: string) {
const command = new GetObjectCommand({ Bucket: process.env.S3_BUCKET!, Key: key });
return getSignedUrl(s3, command, { expiresIn: 900 });
}
sau CLIYou can also inspect and manage environment storage files directly from the sau CLI (storage:read / storage:write scopes):
sau storage files-list --provider environment --path / -o table
Verify that an unsigned request to the object URL returns 403 Forbidden, while the presigned URL returns 200 OK and the exact JSON payload:
# 1. Unsigned direct URL must be rejected (403)
curl -s -o /dev/null -w "%{http_code}\n" "https://s3.example-storage.com/prod-media-assets/releases/sample-manifest.json"
# 2. Presigned URL succeeds (200)
SIGNED_URL=$(aws --profile sau-s3 --endpoint-url https://s3.example-storage.com \
s3 presign s3://prod-media-assets/releases/sample-manifest.json --expires-in 300)
curl -fsSL "$SIGNED_URL"
PUT upload to a presigned URL fails with a CORS error. Configure a bucket CORS rule permitting PUT and GET exclusively from your production origin (https://app.example.com) with AllowedHeaders: ["Content-Type"]—never AllowedOrigins: ["*"] on authenticated upload buckets.SignatureDoesNotMatch on presigned PUT. If you sign ContentType: 'image/png' inside PutObjectCommand, the browser's fetch(uploadUrl, { method: 'PUT', headers: { 'Content-Type': 'image/png' } }) must send the exact same Content-Type header.RequestTimeTooSkewed). S3 Signature v4 rejects requests if the server clock drifts more than 15 minutes from UTC; verify timedatectl status shows System clock synchronized: yes.tenants/<tenantId>/<uuid>) and set Content-Disposition: attachment on untrusted user files so an uploaded SVG or HTML file can never execute scripts.7 days so abandoned browser uploads do not accrue storage charges.S3_SECRET_ACCESS_KEY in Access > Key vault & KMS (/dashboard/key-vault).Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.