Cloud Storage HTTP API Overview
CloudBase Cloud Storage offers two sets of HTTP APIs targeting different environment types. By default, use the PG mode set; classic environments should use the classic mode set.
Two cloud storage HTTP APIs
| Dimension | PG Cloud Storage | Classic Cloud Storage |
|---|---|---|
| Applicable environment | PG environments (default) | Classic environments |
| Authentication | CloudBase AccessToken (Authorization: Bearer <token>) | JWT Bearer Token (service_role / authenticated / anon) |
| Upload path | Goes through Storage API → COS; metadata is coordinated transactionally | Client SDK gets a signature and uploads directly to COS |
| Permission model | PostgreSQL RLS policies (SQL) | Bucket-level built-in permissions + JSON security rules |
| API surface | Full Bucket / Object CRUD, signed URLs, object metadata, multipart upload | Basic object upload / download / delete / copy |
How to choose
- PG environments → PG Cloud Storage HTTP API
- Classic environments → Classic Cloud Storage HTTP API
- Not sure which environment you're on → Check the environment overview in the CloudBase Console, or read the PG mode overview
Product docs
If you want to understand the full capabilities of cloud storage (console, SDK, CLI, cosBrowser, etc.) — not just the HTTP API:
- PG Cloud Storage — RLS permission model and policy patterns
- Classic Cloud Storage — SDK / console / CDN / Cloud Infinite, etc.