Skip to main content
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog

Loading…

Servers Are Up

Your apps, automation and data on hardware we own. Build a private stack with predictable capacity and access through your dashboard, API or SSH.

SLA with service creditsOwned hardwareUS-based

Make room for your next idea

Explore the capacity, apps and access options that fit your workload. Check current availability and your total before you buy.

Sign up freeView Pricing

Products

  • Linux VPS
  • Windows VPS
  • Cloud & SaaS Services
  • Cloud Storage (Azure)
  • Virtual Datacenter
  • AI & Agent Hosting
  • Containers
  • Instant Apps
  • Software Platforms
  • Network builder
  • Game Servers
  • Pricing

Resources

  • Free Network Tools
  • 2026 Pricing Benchmark
  • Live SVG Badges
  • Latency & Speed Test
  • Guides & Tutorials
  • Documentation
  • API Reference
  • MCP Server
  • CLI & SDKs
  • OpenAPI & llms.txt
  • Use Cases
  • Free Migration
  • Uptime & Reliability
  • Datacenter
  • System Status
  • Network
  • Provider Comparisons Hub
  • Compare Providers

Company

  • About Us
  • Enterprise
  • Security Architecture
  • Trust Center
  • Blog
  • FAQ
  • Compliance
  • Startup Program
  • Open-Source Sponsorship
  • Press & Media Kit
  • Referral Program
  • Help Center
  • Contact Us
© Servers Are Up
TermsPrivacySLARefund PolicyDPAAcceptable Use
Service information
Docs
  • Documentation Hub
  • Choose a Product
    VMs, Containers & Cloud
  • First Linux Server
    SSH, Firewall & Apps
  • Windows Server 2025
    BYOL & Remote Desktop
  • Remote Access
  • Troubleshooting
  • FAQ
  • All Product Guides
    29 Step-by-Step Guides
  • Cloud & SaaS Catalog
    112 Cloud & SaaS Offerings
  • Azure Cloud Storage
    Hot/Cool/Archive & WORM
  • Resource Manager & RBAC
    Groups, Tags & Locks
  • Multi-Model Cloud DB
    JSONB, SQL & pgvector
  • Cloud Identity & ZTNA
    OIDC, SCIM & PIM
  • Key Vault & KMS
    Secrets & Envelope Keys
  • Cloud SIEM, SOAR & DLP
    Posture & Threat Response
  • API Gateway & Cloud DNS
    Edge WAF & DNS Zones
  • Serverless, Workflows & IoT
    Functions, Queues & DAGs
  • SaaS, Governance & Vault
    Budgets & Off-Host GRS
  • Build Web Apps with AI
  • Next.js and React
  • TypeScript and Node.js
  • npm and Tooling
  • Data and APIs
  • Deploy and Operate
  • Tutorials
  • Infrastructure
  • Automation & Regions
  • API Overview
  • API v1 Reference
    Endpoints & 23 Scopes
  • MCP Server
    129 AI Agent Tools
  • Swagger / OpenAPI 3.1
  • API Playground
  • Versioning & Sunset
  • API Token Security
    Authentication & Tokens
  • Instances API
    Compute Resources
  • Networking API
    Networks & Ports
  • Storage API Availability
    Volumes & Backups
  • Webhooks & Events
    Event Notifications
  • Rate Limits & Best Practices
    Throttling & Retries
  • sau CLI Reference
    34 Commands (v0.2)
  • Browser Web CLI
  • SDKs
  • Infrastructure as Code
    Terraform & Ansible
  • Code Examples
  • CLI & SDK Guides
  • Security Guides
  • Security at a Glance
  • Zero Trust Architecture
  • Live Trust Center
  • Compliance
Need help?

Loading documentation...

Documentation/products

Create an S3 bucket, upload files and issue signed URLs

Link S3-compatible object storage in your Servers Are Up environment, upload objects with AWS CLI or rclone and generate presigned URLs.

Beginner
16 min
Updated 2026-11-12

Deploy Ready-to-Run Infrastructure in Seconds

Linux VMs from $6/mo · Pooled Virtual Datacenters from $12/mo · Use code WELCOME20 for 20% off your first order.

Browse ServersView Pricing

Commands checked on 2026-11-12 with AWS CLI v2.18, rclone 1.68, Node.js 24, sau CLI 0.2.0.

What you will have at the end

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.

Before you start

  • A Servers Are Up account signed in at /dashboard.
  • Decide which object storage backend fits your workload:
    • S3-Compatible Object Storage (/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.
    • Managed Cloud Storage Hosted via Microsoft Azure (/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.

Steps

1. Create or link a private bucket in your environment

  1. Open Storage > Storage (/dashboard/storage) and select the Buckets / Object Storage view.
  2. Connect your S3-compatible endpoint (region, HTTPS endpoint URL, scoped Access Key ID, and Secret Access Key) and create or register a private bucket such as prod-media-assets.
  3. Keep Public bucket listing / anonymous read disabled—every customer upload or invoice PDF should remain private and be served only via time-limited signed URLs.

2. Configure a scoped profile in AWS CLI v2 or rclone

Configure 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/

3. Generate short-lived presigned URLs from CLI and TypeScript

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 });
}

4. Inspect environment files via the sau CLI

You 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

Check that it works

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"

What can go wrong

  • Browser 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.
  • Clock skew (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.

Good practice

  • Never trust user-supplied filenames when building object keys; generate random UUIDv4/ULID keys under a tenant prefix (tenants/<tenantId>/<uuid>) and set Content-Disposition: attachment on untrusted user files so an uploaded SVG or HTML file can never execute scripts.
  • Add an automatic lifecycle rule to abort incomplete multipart uploads after 7 days so abandoned browser uploads do not accrue storage charges.
  • Store your S3_SECRET_ACCESS_KEY in Access > Key vault & KMS (/dashboard/key-vault).

Where to go next

  • Purchase Azure-backed cloud storage with WORM locks and SAS
  • Connect DigitalOcean Spaces, R2, S3 and iSCSI cloud drives
  • Snapshot a server before a change and restore safely

Related Articles

Create a scoped API key and send your first v1 request

Read more

Route APIs with Edge WAF, rate limits and Cloud DNS

Read more

Purchase Azure-backed cloud storage with WORM locks and SAS

Read more

Frequently Asked Questions

What does the Create an S3 bucket, upload files and issue signed URLs documentation guide cover?
Link S3-compatible object storage in your Servers Are Up environment, upload objects with AWS CLI or rclone and generate presigned URLs. It is rated beginner difficulty (16 min) and applies to Servers Are Up infrastructure and workflows.
Can I manage or automate these steps through the Servers Are Up dashboard, REST API v1, or MCP server?
Yes. Every Servers Are Up server includes browser-based SSH, WebRDP, and VNC console access in the dashboard, plus programmatic control via the REST API v1 (/api/v1) and hosted Model Context Protocol server (/api/mcp/v1) using a scoped Personal Access Token.

Need hands-on help with Create an S3 bucket, upload files and issue signed URLs?

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.

Was this article helpful?

On this page

What you will have at the endBefore you startSteps1. Create or link a private bucket in your environment2. Configure a scoped profile in AWS CLI v2 or rclone3. Generate short-lived presigned URLs from CLI and TypeScript4. Inspect environment files via the sau CLICheck that it worksWhat can go wrongGood practiceWhere to go next