Netrunner's Guide to AWS SES: Hacking Communication Barriers
summary
Claims production system sends 500,000 emails daily, uses Amazon SES plus SQS SNS CloudWatch Lambda and S3 for copies, and enforces SPF DKIM and custom MAIL FROM and DMARC for deliverability. Describes pitfalls: sandbox limits, Apple Private Relay bounces, shared vs dedicated IPs, blacklist checks, and prewarming. Shows concrete rate‑limit strategies: chunking, SQS+DLQ retry, and a heartbeat Lambda orchestrator that adjusts concurrency per second to fill capacity without throttling, with dashboards in QuickSight.
AI-written summary · about
chapters (13)
- 0:00Introduction and Welcome
- 0:33Speaker Introduction
- 2:07Company Overview
- 2:54Importance of Communication
- 3:25Amazon SES Overview
- 4:13Email Sending Best Practices
- 5:22Security and Compliance
- 6:04Technical Integration with SES
- 10:15Domain and Email Validation
- 23:24Handling Email Metrics and Limits
- 27:09Advanced SES Configuration
- 40:05Event Handling and Monitoring
- 48:32Conclusion and Final Thoughts
related talks
56mEmail vs Capitalism, or, Why We Can't Have Nice Things
39mRed Teaming from outside: Identifying and exploiting SaaS systems... (Rojan Rijal)
12mImplementing Email Attachment Security
28m10 Billion Messages in a Day, How We Built the Infrastructure That Delivers
40mSh... Fail Happens: Fail-aware Events Processing on AWS
29mHow to Handle 1 Billion Emails?
31mHow to Write Terrible Emails Well?
28mCostly mistakes in serverless computing