Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add account-wide alarms for SES sender reputation #1821

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jameshochadel
Copy link
Contributor

@jameshochadel jameshochadel commented Jan 7, 2025

Changes proposed in this pull request:

  • Alarms trigger at warning and critical levels if SES reputation metrics are in danger of putting our account under review
  • The platform operations team is alerted through our usual notification channels
  • Related to Monitor AWS sender reputation product#3214

security considerations

Follows standard approach for CloudWatch alarms.

@jameshochadel jameshochadel requested a review from a team as a code owner January 7, 2025 15:44
Comment on lines +91 to +92
period = 300
stat = "Average"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question for all of these, I think:
is the BounceRate cumulative or bucketed? When AWS evaluates whether we're good senders, what window are they looking at?

(reading AWS's docs it sounds like the answer to the second question is "maybe")

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The best answer I can find is from this page, which says:

We calculate your bounce rate based on a representative volume of email. A representative volume is an amount of email that represents your typical sending practices. To be fair to both high- and low-volume senders, the representative volume is different for each account and changes as the account's sending patterns change.

So it sounds like they sample delivery notifications. That doesn't explain if the thresholds are instantaneous or averaged over some period of time, though. Are there changes you'd like to see here if it's one or the other?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants