better handling of frequent email alerts

[afeld]

Background Information

We get a bunch of emails, and it's not always clear if we need to act on them, or how best to do so. Example subject lines:

• Let's Encrypt certificate expiration notice
  • This email usually means they are using the deprecated cloud.gov custom domain / CDN service. cloud.gov is working to migrate folks, so for Federalist/cloud.gov sites, we can ignore (ideally filter out).
• DotGov Domain <whatever>.gov is due for renewal
• AWS
  • Your AWS Abuse Report
  • deprecation notice
  • AWS Budgets: <budget> has exceeded your alert threshold
  • Attention required on case
  • Amazon EC2 Instance Retirement
  • Amazon EC2 Maintenance: Instance scheduled for retirement

Implementation Steps

• [ ] Split out issues for things to do besides documenting what to do with them, such as:
  • Updating contacts for AWS accounts to ensure AWS alerts go directly to relevant teams - https://github.com/18F/tts-tech-portfolio/issues/1142
  • Automatically create issues for domain renewals - https://github.com/18F/tts-tech-portfolio/issues/882
• [x] Update Ops Rotation checklist/documentation
• [ ] Unsubscribe / filter out things we don't need to care about
• [ ] CloudWatch alerts for program teams should be directed to them and skip our inbox

Acceptance Criteria

• [ ] For alerts that (will still) regularly come to Tech Portfolio mailing lists, have documented procedure for handling

[rocheller123]

AWS and CloudWatch email alerts will eventually be sent to the relevant contact's email address directly. Therefore, Tech Portfolio may not be required to send AWS-related emails to the programs.