Backup operations
Every Backup operation Overcast declares — 18 of 18 implemented — with status, behaviour notes and a link to the AWS API reference for each.
All 18 listed operations are implemented. Back to Backup.
Summary
| Category | ✅ Supported | ⚠️ Partial |
|---|---|---|
| Operations | 7 | 11 |
Endpoints
Operations
| Operation | Status | Notes | AWS Docs |
|---|---|---|---|
CreateBackupVault | ✅ Supported | PUT /backup-vaults/{BackupVaultName}; BackupVaultTags is applied at create time, in the same store write as the vault (#1195) | docs |
DeleteBackupVault | ✅ Supported | DELETE /backup-vaults/{BackupVaultName}; empty 200, the modeled Unit output | docs |
DescribeBackupVault | ⚠️ Partial | GET /backup-vaults/{BackupVaultName}; honours backupVaultAccountId. Vault lock and MPA approval are not emulated, so Locked is always false and the retention members are absent | docs |
ListBackupVaults | ⚠️ Partial | GET /backup-vaults; vaultType, shared, maxResults and nextToken query params. Every vault is a standard unshared vault, so shared=true lists none | docs |
CreateBackupPlan | ⚠️ Partial | PUT /backup/plans; BackupPlanTags is applied at create time (#1195); AdvancedBackupSettings is not stored or returned | docs |
DeleteBackupPlan | ✅ Supported | DELETE /backup/plans/{BackupPlanId}; returns the modeled id, ARN, VersionId and DeletionDate | docs |
GetBackupPlan | ⚠️ Partial | GET /backup/plans/{BackupPlanId}; only the current version is kept, so any other versionId is not found, and MaxScheduledRunsPreview yields no ScheduledRunsPreview | docs |
ListBackupPlans | ⚠️ Partial | GET /backup/plans; maxResults and nextToken query params. Plans are deleted outright rather than tombstoned, so includeDeleted adds nothing | docs |
UpdateBackupPlan | ⚠️ Partial | POST /backup/plans/{BackupPlanId}; mints a new VersionId per update. Prior versions are not retained and AdvancedBackupSettings is not stored | docs |
CreateBackupAccessPoint | ⚠️ Partial | PUT /backup-access-point/create (#1467); Tags is applied at create time. AccessPointPolicy is accepted and dropped — no access policy is enforced behind this control plane | docs |
DeleteBackupAccessPoint | ✅ Supported | DELETE /backup-access-point/delete/{AccessPointArn}; empty 204, the modeled Unit output | docs |
DescribeBackupAccessPoint | ⚠️ Partial | GET /backup-access-point/{AccessPointArn}; returns the stored AccessPointMetadata verbatim. No recovery point exists to read BackupVaultName, BackupVaultArn, ResourceArn or ResourceType from, and no S3 access point is created, so those members and the metadata’s S3AccessPointArn/S3AccessPointAlias are absent rather than invented | docs |
ListBackupAccessPoints | ⚠️ Partial | GET /backup-access-point; MaxResults and NextToken query params. Members read off a recovery point are absent, as on DescribeBackupAccessPoint | docs |
ListBackupAccessPointsByRecoveryPoint | ⚠️ Partial | POST /backup-access-point/recovery-point/{RecoveryPointArn}; filters on the ARN each access point was created against. No backup job runs, so no recovery point Overcast produced can ever be named here and the list is empty | docs |
ListBackupAccessPointsByResource | ⚠️ Partial | POST /backup-access-point/resource/{ResourceArn}; an access point’s ResourceArn is a property of its recovery point, which Overcast never creates, so nothing is ever stored for this to match and the list is empty | docs |
TagResource | ✅ Supported | POST /tags/{ResourceArn}, shared with Pipes/EKS/Scheduler/AppConfig/API Gateway’s ARN-dispatched path (#1195). Tags are stored inline on the vault, plan or access point record, so they die with it | docs |
ListTags | ✅ Supported | GET /tags/{ResourceArn} (#1195) | docs |
UntagResource | ✅ Supported | POST /untag/{ResourceArn} — Backup’s own path, not another member of the shared /tags dispatcher (#1195) | docs |
Related
- Backup — quick start, what works, and the differences from AWS
- All service pages