Monitoring Email Deliverability via Syslog during AWS SES Migration
Last Updated:
Overview
To meet FRM compliance requirements, Okta will be gradually migrating the primary email provider for the default Okta domain (noreply@okta.com) from SendGrid to FedRAMP-authorized AWS SES for FRM cells. During this time, customers will see a gradual increase in the proportion of their outgoing emails routed via AWS SES.
Okta provides admins with visibility into email delivery events through the Okta System Log which can be useful in identifying any provider specific deliverability issues during the migration.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Email Notification
Solution
Using Syslog to Monitor Deliverability:
Customers who wish to monitor their email traffic or track specific deliverability metrics during the cutover can rely on Okta's System Log.
- Identifying the Email Provider: The email provider (either SendGrid or SES) used to route a specific email will be visible in the existing system.email.delivery syslog event. You can identify which provider handled the message by looking at the informative message values contained within the debugData field of the syslog event.
- Monitoring the Ramp-Up: By tracking the email provider specified in the debugData, administrators can precisely monitor email deliverability as their organizational traffic is slowly shifted from SendGrid to SES.
Additional Information
Dual-Provider Syslog Events During Migration: Certain actions may trigger syslog events that reference both SendGrid and SES in the informative message values contained within the debugData.
For example, to prevent deliverability drops during the transition, Okta is actively handling bounce removal for both providers. Therefore, syslog event system.email.bounce.removal would reference both providers during the migration timeframe.
Related References
