winterbaume-workspacesweb
Amazon WorkSpaces Web service implementation for winterbaume.
This crate is part of the winterbaume workspace — a suite of in-process AWS service mocks for Rust. Use the umbrella winterbaume crate to pull in all services at once, or depend on this crate directly for WorkSpaces Web 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 | WorkSpaces Web |
| AWS model | workspaces-web |
| Protocol | restJson1 |
| winterbaume coverage | 68/75 operations (90.7%) |
| stubs (routed, returns empty/default) | 0/75 operations (0.0%) |
| moto coverage | 27/75 operations (36.0%) |
| floci coverage | 0/75 operations (0.0%) |
| kumo coverage | 0/75 operations (0.0%) |
| Coverage report date | 2026-05-06 |
Coverage is generated from .agents/docs/API_COVERAGE.md by 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 for setup, usage, and the full cross-service coverage table.
Server-mode usage
Start winterbaume-server and point the AWS CLI at it:
Current Network Resource Stub Semantics
WorkSpaces Web currently stores portal networking as portal/resource metadata.
- Portal and network settings shapes include VPC ID, subnet IDs, and security group IDs.
- Current implemented state records those values only where the surrounding resource handler persists the portal or settings object.
- Browser session lifecycle does not create VPC endpoints or ENIs.
- The implementation does not consult
winterbaume-ec2state for these identifiers, so it does not check that referenced VPCs, subnets, security groups, VPC endpoints, network interfaces, or load balancers exist, belong to the same VPC, or are in a usable lifecycle state.
Example
use BehaviorVersion;
use MockAws;
use WorkspacesWebService;
async
Implemented APIs (68)
AssociateBrowserSettingsAssociateDataProtectionSettingsAssociateNetworkSettingsAssociateSessionLoggerAssociateTrustStoreAssociateUserAccessLoggingSettingsAssociateUserSettingsCreateBrowserSettingsCreateDataProtectionSettingsCreateIdentityProviderCreateNetworkSettingsCreatePortalCreateSessionLoggerCreateTrustStoreCreateUserAccessLoggingSettingsCreateUserSettingsDeleteBrowserSettingsDeleteDataProtectionSettingsDeleteIdentityProviderDeleteNetworkSettingsDeletePortalDeleteSessionLoggerDeleteTrustStoreDeleteUserAccessLoggingSettingsDeleteUserSettingsDisassociateBrowserSettingsDisassociateDataProtectionSettingsDisassociateNetworkSettingsDisassociateSessionLoggerDisassociateTrustStoreDisassociateUserAccessLoggingSettingsDisassociateUserSettingsExpireSessionGetBrowserSettingsGetDataProtectionSettingsGetIdentityProviderGetNetworkSettingsGetPortalGetPortalServiceProviderMetadataGetSessionGetSessionLoggerGetTrustStoreGetTrustStoreCertificateGetUserAccessLoggingSettingsGetUserSettingsListBrowserSettingsListDataProtectionSettingsListIdentityProvidersListNetworkSettingsListPortalsListSessionLoggersListSessionsListTagsForResourceListTrustStoreCertificatesListTrustStoresListUserAccessLoggingSettingsListUserSettingsTagResourceUntagResourceUpdateBrowserSettingsUpdateDataProtectionSettingsUpdateIdentityProviderUpdateNetworkSettingsUpdatePortalUpdateSessionLoggerUpdateTrustStoreUpdateUserAccessLoggingSettingsUpdateUserSettings
AssociateIpAccessSettingsCreateIpAccessSettingsDeleteIpAccessSettingsDisassociateIpAccessSettingsGetIpAccessSettingsListIpAccessSettingsUpdateIpAccessSettings