This guide documents the new AWS Wickr administration console, released on March 13, 2025. For documentation on the classic version of the AWS Wickr administration console, see Classic Administration Guide.
Limitations
The following features are not supported through AWS PrivateLink and require internet connectivity:
-
Wickr Open Access (WOA)
-
Client Application Updates
-
Mobile Apps (iOS/Android)
-
Source: App Store/Google Play Store
-
Requirement: Internet access required
-
-
Desktop Applications
-
Windows/Mac: Uses global S3 endpoints (not AWS PrivateLink compatible)
-
Linux: Uses Snap Store (requires internet access)
-
-
-
Debugging and Telemetry
-
Crash reports
-
Debug metrics
-
Client-side analytics links
-
-
Mobile Push Notifications
These services require internet connectivity and cannot use AWS PrivateLink:
-
Apple Push Notifications
-
Requirement: Direct internet access
-
Ports: 443, 2195, 2196, 5223
-
Reference: Apple Support Documentation
-
-
Google/Android Notifications
-
Requirement: Firebase Cloud Messaging access
-
Reference: Firebase Documentation
-
-
-
AWS Wickr Console is not currently supported for Private Access. For more information, see Supported AWS Regions, service consoles, and features for Private Access.
Minimum required client versions for AWS PrivateLink
The following client versions have been validated with AWS PrivateLink:
-
iOS 6.64 (where applicable)
-
Android 6.60 (where applicable)
-
Desktop clients 6.60
-
Bots 6.60
Features requiring additional configuration
Wickr Bots
-
Requirement: Customer-managed infrastructure
-
Action: Configure network paths for bot dependencies
-
Consideration: Ensure bots can reach required AWS services through VPC endpoints
File Downloads
-
S3 Connectivity: Required for file operations (except Frankfurt region)
-
Solution: Create S3 VPC gateway endpoint
-
Reference: AWS PrivateLink for Amazon S3
