Implementing Email Attachment Security
summary
Claims a working pipeline that creates P minip Library password‑protected .jip files, uploads them to S3, and sends short‑lived S3 pre-signed URLs via SES. Shows concrete choices: compression level 0–10, password sourced from user data, SES throttling workarounds for the 40 emails/sec limit, and Lambda layers to bundle the library. Demonstrates numbers (URL expiry: 6 hours vs 36 vs 7 days), latency savings from no attachments, and end‑to‑end code snippets.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:14introduction and speaker background
- 0:27business scenario: email attachments
- 1:10risks associated with email attachments
- 1:48solutions for email attachment security
- 4:22implementing security with pyminigip
- 5:57aws integration for enhanced security
- 9:33final implementation and benefits
- 11:42conclusion and contact information
related talks
51mNetrunner's Guide to AWS SES: Hacking Communication Barriers
43mSimplify and accelerate security for simple storage: Case studies (PRT276)
20mAmazon S3 presigned URL security
18mImproving your Amazon S3 security with cost-effective practices
19mDemo - S3 Object Lambda
26mProtecting your data in Amazon S3
15mSupplement your AWS security with JIT access and CNAPP
55mHandling secrets in cloud-based applications