SaaS products Ledgerly Backup destinations
Backup destinations · Ledgerly
S3-compatible targets where this app's backups are written.
| Name | Target | Status | |
|---|---|---|---|
| ledgerly-backups | AWS S3 · us-west-2 | Enabled · object-lock on | |
| cold-archive | S3-compatible · Wasabi | Enabled | |
| old-bucket | AWS S3 · us-east-1 | Disabled |
About this page
Where backup copies are kept. Use platform storage or plug in your own destination — your own cloud bucket, your own rules. Destinations are tested when you add them, so a backup never fails at the moment you need it because of a typo made months ago.
Behind this page/apps/:saasAppId/backup-destinations · CanManageBackups
Retrieve
sp_Builder_ListBackupDestinations returns destination metadata: bucket/region, role ARN, external ID, object-lock, and enabled state.Save
Add/edit →sp_Builder_UpsertBackupDestination. Disable is the same proc with @IsEnabled=0 (no separate proc).Success
- Credentials are never returned to the browser.
- Disable is blocked while a job requires the destination.
- Object-lock state is surfaced for compliance.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Page IDbackup-destinations
Route/apps/:saasAppId/backup-destinations
AccessCanManageBackups
Statusexternal-integration-required
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.