External Messaging Services
How to use cloud-native messaging services to send outbound notifications from your Game Warden-deployed application.
External messaging services allow your Game Warden-deployed application to send outbound, no-reply messages to users through supported cloud-native tools. These services can deliver emails, pub/sub events, or webhooks using providers like AWS, GCP, or Azure.
The information in this guide helps you build secure, compliant, and effective user messaging into your application, without violating DOW or Game Warden requirements.
Supported messaging types
Game Warden supports the following message types:
| Message Type | Supported Providers | Description |
|---|---|---|
| AWS SES, SendGrid, Mailgun | Send outbound, no-reply emails | |
| Pub/Sub | GCP Pub/Sub, Azure SB | Broadcast internal or external events |
| Webhooks | Custom HTTPS endpoints | Connect with third-party systems |
Template configuration
You can define custom message templates that originate from within your application and serve specific use cases. Below are some common use cases:
| Use Case | Example |
|---|---|
| User Notification | "You have new documents available for download." |
| Credential Expiry Alert | "Your password will expire in 3 days." |
| System Maintenance Notice | "System maintenance is scheduled for 22:00 UTC." |
| Event Trigger Notification | "Your request has been processed successfully." |
Template design guidelines
To ensure compliance and prevent security issues, follow these rules:
- Use generic, non-personalized language (for example, "You have a new message. Log in to view.")
- Do not include Controlled Unclassified Information (CUI) or personal identifiable information
- Avoid CUI markings or classification labels
- Test any dynamic template variables to avoid leaking sensitive content
If CUI data is sent through these services, it may cause data spillage into unauthorized networks or storage systems.
Customer responsibilities
Game Warden cannot determine which data is CUI across all customer applications. Your team must:
- Work with your Mission Owner to identify what qualifies as CUI
- Ensure message templates do not expose sensitive data
- Prevent unauthorized distribution of CUI through external services
If you suspect a CUI data spillage, report the incident immediately by following the procedure outlined in the Customer Incident Reporting Procedure.
Have questions
If you're unsure about your messaging integration or compliance boundaries, contact your Mission Success Manager (MSM).