winterbaume-backup 0.2.0

<!-- BEGIN AUTO (generated by .agents/skills/update-readme/scripts/update_readme.py) -->

# winterbaume-backup

AWS Backup service implementation for winterbaume.

This crate is part of the [winterbaume](https://github.com/moriyoshi/winterbaume) workspace — a suite of in-process AWS service mocks for Rust. Use the umbrella [`winterbaume`](https://crates.io/crates/winterbaume) crate to pull in all services at once, or depend on this crate directly for Backup only.

Winterbäume is not affiliated with, endorsed by, or sponsored by Amazon Web Services, Inc. or Amazon.com, Inc. Amazon Web Services, AWS, and related marks are trademarks of Amazon.com, Inc. or its affiliates. All other trademarks are the property of their respective owners.

## Coverage

| Metric | Value |
|---|---|
| Service | Backup |
| AWS model | `backup` |
| Protocol | restJson1 |
| winterbaume coverage | 105/108 operations (97.2%) |
| stubs (routed, returns empty/default) | 3/108 operations (2.8%) |
| moto coverage | 17/108 operations (15.7%) |
| floci coverage | 0/108 operations (0.0%) |
| kumo coverage | 12/108 operations (11.1%) |
| Coverage report date | 2026-05-13 |

Coverage is generated from [`.agents/docs/API_COVERAGE.md`](../../.agents/docs/API_COVERAGE.md) by [`update_readme.py`](../../.agents/skills/update-readme/scripts/update_readme.py). The `winterbaume` row counts only operations with real, state-backed logic; `stubs` counts handlers that route the request and return an empty/default response without real behaviour. Operation-count coverage is a prioritisation signal, not a behavioural guarantee.

See the workspace [`README.md`](../../README.md) for setup, usage, and the full cross-service coverage table.

## Server-mode usage

Start `winterbaume-server` and point the AWS CLI at it:

```sh
cargo run -p winterbaume-server -- --host 127.0.0.1 --port 5555
```

```sh
export AWS_ENDPOINT_URL=http://localhost:5555
aws backup list-backup-plans
```

## Example

```rust
use aws_sdk_backup::config::BehaviorVersion;
use winterbaume_backup::BackupService;
use winterbaume_core::MockAws;

#[tokio::main]
async fn main() {
    let mock = MockAws::builder()
        .with_service(BackupService::new())
        .build();

    let config = aws_config::defaults(BehaviorVersion::latest())
        .http_client(mock.http_client())
        .credentials_provider(mock.credentials_provider())
        .region(aws_sdk_backup::config::Region::new("us-east-1"))
        .load()
        .await;

    let client = aws_sdk_backup::Client::new(&config);

    let resp = client
        .list_backup_vaults()
        .send()
        .await
        .expect("list_backup_vaults should succeed");
    println!("Backup vaults: {}", resp.backup_vault_list().len());
}
```

## Implemented APIs (105)

- `AssociateBackupVaultMpaApprovalTeam`
- `CancelLegalHold`
- `CreateBackupPlan`
- `CreateBackupSelection`
- `CreateBackupVault`
- `CreateFramework`
- `CreateLegalHold`
- `CreateLogicallyAirGappedBackupVault`
- `CreateReportPlan`
- `CreateRestoreAccessBackupVault`
- `CreateRestoreTestingPlan`
- `CreateRestoreTestingSelection`
- `CreateTieringConfiguration`
- `DeleteBackupPlan`
- `DeleteBackupSelection`
- `DeleteBackupVault`
- `DeleteBackupVaultAccessPolicy`
- `DeleteBackupVaultLockConfiguration`
- `DeleteBackupVaultNotifications`
- `DeleteFramework`
- `DeleteRecoveryPoint`
- `DeleteReportPlan`
- `DeleteRestoreTestingPlan`
- `DeleteRestoreTestingSelection`
- `DeleteTieringConfiguration`
- `DescribeBackupJob`
- `DescribeBackupVault`
- `DescribeCopyJob`
- `DescribeFramework`
- `DescribeGlobalSettings`
- `DescribeProtectedResource`
- `DescribeRecoveryPoint`
- `DescribeRegionSettings`
- `DescribeReportJob`
- `DescribeReportPlan`
- `DescribeRestoreJob`
- `DescribeScanJob`
- `DisassociateBackupVaultMpaApprovalTeam`
- `DisassociateRecoveryPoint`
- `DisassociateRecoveryPointFromParent`
- `ExportBackupPlanTemplate`
- `GetBackupPlan`
- `GetBackupPlanFromJSON`
- `GetBackupSelection`
- `GetBackupVaultAccessPolicy`
- `GetBackupVaultNotifications`
- `GetLegalHold`
- `GetRecoveryPointIndexDetails`
- `GetRecoveryPointRestoreMetadata`
- `GetRestoreJobMetadata`
- `GetRestoreTestingInferredMetadata`
- `GetRestoreTestingPlan`
- `GetRestoreTestingSelection`
- `GetSupportedResourceTypes`
- `GetTieringConfiguration`
- `ListBackupJobSummaries`
- `ListBackupJobs`
- `ListBackupPlanVersions`
- `ListBackupPlans`
- `ListBackupSelections`
- `ListBackupVaults`
- `ListCopyJobSummaries`
- `ListCopyJobs`
- `ListFrameworks`
- `ListIndexedRecoveryPoints`
- `ListLegalHolds`
- `ListProtectedResources`
- `ListProtectedResourcesByBackupVault`
- `ListRecoveryPointsByBackupVault`
- `ListRecoveryPointsByLegalHold`
- `ListRecoveryPointsByResource`
- `ListReportJobs`
- `ListReportPlans`
- `ListRestoreJobSummaries`
- `ListRestoreJobs`
- `ListRestoreJobsByProtectedResource`
- `ListRestoreTestingPlans`
- `ListRestoreTestingSelections`
- `ListScanJobSummaries`
- `ListScanJobs`
- `ListTags`
- `ListTieringConfigurations`
- `PutBackupVaultAccessPolicy`
- `PutBackupVaultLockConfiguration`
- `PutBackupVaultNotifications`
- `PutRestoreValidationResult`
- `RevokeRestoreAccessBackupVault`
- `StartBackupJob`
- `StartCopyJob`
- `StartReportJob`
- `StartRestoreJob`
- `StartScanJob`
- `StopBackupJob`
- `TagResource`
- `UntagResource`
- `UpdateBackupPlan`
- `UpdateFramework`
- `UpdateGlobalSettings`
- `UpdateRecoveryPointIndexSettings`
- `UpdateRecoveryPointLifecycle`
- `UpdateRegionSettings`
- `UpdateReportPlan`
- `UpdateRestoreTestingPlan`
- `UpdateRestoreTestingSelection`
- `UpdateTieringConfiguration`

<details><summary>Stubbed APIs (3) &mdash; routed but return an empty/default response</summary>

- `GetBackupPlanFromTemplate`
- `ListBackupPlanTemplates`
- `ListRestoreAccessBackupVaults`

</details>

<!-- END AUTO -->