# Migrate DigitalOcean Spaces bucket: Tenant-scoped object prefixes

Move object storage from DigitalOcean Spaces bucket to Ample, one component at a time. Destination verified on Ample: every tenant's objects stored under `tenants//` in a private bucket with an ownership row per object, reads refused for keys outside the caller's prefix or not owned (cross=forbidden), and a prefix-bound listing returning only that tenant's objects (own=1). Source procedure: Inventory the Space with `rclone size` or `s3cmd du`. Not migrated automatically: Spaces CDN settings, CORS rules and per-object ACLs are not migrated; publish an Ample bucket for public delivery. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep the Space read-only until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## Representative Queries
- Migrate DigitalOcean Spaces bucket: Tenant-scoped object prefixes
- Where can I host Tenant-scoped object prefixes?
- I need a component-scoped export/import or reconfiguration procedure for Tenant-scoped object prefixes, with compatibility checks, verification and rollback.

## Migration Source
**DigitalOcean Spaces bucket**

## Workload
**Tenant-scoped object prefixes**

## Resource Requirements
- S3-compatible object storage

## Infrastructure Requirements
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
- Authorized access to the DigitalOcean Spaces bucket source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with `servers:write`, `buckets:write`

## Workflow Steps
1. **Inventory the source**: List what DigitalOcean Spaces bucket provides beyond the component you are moving. Out of scope here: Spaces CDN settings, CORS rules and per-object ACLs are not migrated; publish an Ample bucket for public delivery.
2. **Source step 1**: Inventory the Space with `rclone size` or `s3cmd du`
3. **Source step 2**: Copy objects with `rclone sync` from the Spaces endpoint to the Ample bucket endpoint using the issued credentials (path-style)
4. **Source step 3**: Verify a sample of objects by size and checksum after the copy
5. **Create the destination bucket and copy**: Create the bucket, copy with rclone or the S3 CLI in path-style mode using the issued credentials, then pass the credentials to the app as encrypted S3_* variables.
   - **Command:** `ample bucket create --name `
6. **Validate before cutover**: Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/tenant-scoped-object-prefixes).
7. **Cut over**: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep the Space read-only until confirmed.
8. **Rollback**: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Examples
- **Express pattern fixture (destination)**: Verified destination basis: tenant-scoped object prefixes.

## Success Checks
- The destination app responds on its public URL
- Tenant-scoped-object-prefixes check from the destination example
- Data or object counts and checksums match the source

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from DigitalOcean Spaces bucket's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- No full source-product parity is claimed: Spaces CDN settings, CORS rules and per-object ACLs are not migrated; publish an Ample bucket for public delivery.

## Cost Estimate
- Currency: USD
- Monthly Amount: 5.0
- Components:
  - **App server**: size `s-1vcpu-1gb`, quantity 1.0, monthly amount 5.0

## Evidence Summary
- Destination side verified: the Express pattern fixture deployed on Ample and its checks passed. The source-side export from DigitalOcean Spaces bucket is documented from the vendor's standard tooling and was not executed by this catalog's evidence.

## Formats
- [HTML Format](/content/migrate/digitalocean-spaces-bucket/tenant-scoped-object-prefixes/index.html)
- [Markdown Format](/content/migrate/digitalocean-spaces-bucket/tenant-scoped-object-prefixes.md)
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Adigitalocean-spaces-bucket%3Atenant-scoped-object-prefixes)
