rds.backups.deleteDelete a backup taken by hand that is kept until deleted
Older than the retention window, it is expired at once and the node removes it from the repository within a minute; inside the window it follows the window from now on. A backup that follows the window anyway is refused with 409.
Request syntax
DELETE /rds/api/instances/{id}/backups/{backupId}Path parameters
idRequiredstring
Constraints: 3-64 chars, /^(?!ewdoc-)[a-z0-9-]+$/
backupIdRequiredstring
Response
200 with { backupId, expired }: expired is true when it is removed now, false when it now follows the retention window.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
backupIdAlwaysstring
The backupexpiredAlwaysboolean
true: removed now; false: it now follows the retention window
Checked against the handlers: every route test validates their answers against this schema.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow rds:DeleteBackup on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud rds backups delete id backupIdcurl -X DELETE "https://console.platform-development.deutschecloud.app/rds/api/instances/id/backups/backupId" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_rds_backups_delete.