AWS Wickr Gets Managed Data Retention for Premium Users
AWS Wickr's new Data Retention Service gives Premium customers a serverless, cloud-native way to archive encrypted conversations without running their own containers.
Does AWS Wickr support data retention and message archiving?
Yes. As of July 23, 2026, AWS Wickr Premium customers can enable a managed Data Retention Service that archives conversations across their network. The feature covers direct messages, Groups, and Rooms, including exchanges with external federated teams, while preserving Wickr's end-to-end encryption.
What problem does this solve?
Before this feature, organizations that needed to retain Wickr conversations had to run container-based retention infrastructure themselves. Managing that infrastructure carries ongoing operational overhead, from patching to capacity planning. The new service offloads all of that to AWS.
The serverless architecture means AWS handles deployment, scaling, and monitoring automatically. Organizations that need audit trails for compliance purposes, such as financial services firms or government agencies, no longer have to maintain separate retention pipelines alongside their Wickr deployment.
What exactly gets retained?
The service captures conversations inside the customer's Wickr network, specifically:
- Direct messages between users
- Groups and Rooms involving internal members
- Federated conversations between internal users and external teams
Notably, the retention operates within Wickr's existing encryption model. AWS says end-to-end encryption standards are maintained, though the documentation does not elaborate on the key management mechanics in this announcement.
How do customers enable it?
Data Retention Service is opt-in for existing Wickr Premium subscribers. There is no indication in the announcement of a separate add-on charge; it is presented as a feature available to the Premium tier. Customers interested in enabling it are directed to the AWS Wickr documentation.
Where is it available?
The service launched across nine AWS regions and one GovCloud region:
| Region | Location |
|---|---|
| US East (N. Virginia) | United States |
| Canada (Central) | Canada |
| Asia Pacific (Sydney) | Australia |
| Asia Pacific (Tokyo) | Japan |
| Asia Pacific (Singapore) | Singapore |
| Europe (Frankfurt) | Germany |
| Europe (Stockholm) | Sweden |
| Europe (Zurich) | Switzerland |
| AWS GovCloud (US-West) | United States (Gov) |
The GovCloud region inclusion is notable: it signals that AWS is positioning the feature for US federal agencies and defense contractors that operate within regulated cloud environments.
Why serverless?
The shift from containers to a serverless model carries practical implications for IT teams. There is no cluster to provision, no container images to update, and no minimum capacity to pay for during low-usage periods. Automatic scaling means retention throughput adjusts as message volume fluctuates, which can be useful for organizations with uneven communication patterns across time zones or business cycles.
Comprehensive monitoring is included, though the announcement does not specify which AWS observability tools, such as CloudWatch, are integrated.
Bigger picture
AWS Wickr was originally built around the premise that enterprise collaboration should not require organizations to choose between strong encryption and operational compliance requirements. Features like data retention have historically been the sticking point: end-to-end encryption, by design, limits what a service provider can see or store.
By managing retention at the network level while claiming encryption standards are maintained, AWS is attempting to address that tension for compliance-heavy industries. Organizations evaluating the feature should review the detailed documentation to understand precisely how retained data is stored and who holds access.