Skip to content

How to host a static site on object storage

How-to · Updated Jun 2026

Coming from another cloud?

▸AWS·S3 Static Website

This Quake AI feature maps to AWS’s S3 Static Website.

▸DigitalOcean·Spaces Static Site

This Quake AI feature maps to DigitalOcean’s Spaces Static Site.

How to host a static site on object storage

Serve HTML, CSS, JavaScript, and image files from a Quake AI object storage bucket. For a custom domain or HTTPS at the edge, put a CDN in front of the bucket and point your domain at the CDN.

Prerequisites

Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.

  • An object storage bucket
  • S3 credentials configured in your CLI environment
  • Static site files built locally (index.html, assets)

Upload site files#

Make objects readable#

Apply a public read bucket policy so anonymous GET requests succeed. Test with the tenant-prefixed URL shape:

https://object.<region>.rumble.cloud/<tenant>:<bucket>/index.html

Replace <region>, <tenant>, and <bucket> with your project values.

  1. Point a CDN pull zone or reverse-proxy origin at the bucket endpoint, or at a small reverse-proxy instance that fetches from the bucket.
  2. Follow How to put a CDN in front of a Quake AI workload.
  3. Publish DNS records with How to point a domain at a Quake AI resource (or the CDN provider's CNAME instructions).
  4. Issue TLS at the CDN edge or on the origin with Let's Encrypt.

Verify#

bash
curl -I "https://object.<region>.rumble.cloud/<tenant>:<bucket>/index.html"

Expect HTTP/1.1 200 and a Content-Type appropriate for HTML. After CDN setup, repeat the check against your public hostname.

See also#

Usage Guidelines

The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.

For the full policy, see Usage Guidelines.

Last validated: 27.06.2026

Was this page helpful?