How bikramprasad/email-consumer works
SwiftDrop’s Email Consumer handles SNS notifications: its Lambda parses each message and delegates processing, which checks file and email state in MongoDB, sends receiver emails from an EJS template, updates status, then sends the sender a confirmation. The README also documents SNS subscription and deployment, but those configuration files were not sampled, so deployment wiring is not mapped. The graph reflects sampled calls; SMTP and MongoDB are documented integrations.
Main entry points: sendEmailWithTemplate.js Message processor · emailService.js Template email sender · handler.js Email Lambda · db.js MongoDB connection
Components 9
Event handling
- Email Lambda
handler.js
Email processing
- Message processor
utils/sendEmailWithTemplate.js
Persistence
- MongoDB connection
utils/db.js - Email and file queries
utils/emailDbOps.js
Email delivery
- Template email sender
utils/emailService.js - Receiver and sender templates
templates
Other components
- AWS SNS
- MongoDB
- SMTP service
Connections 9
- AWS SNS → Email Lambda: triggers
README.md - Email Lambda → Message processor: delegates to
handler.js - Message processor → MongoDB connection: connects to
utils/sendEmailWithTemplate.js - Message processor → Email and file queries: queries and updates
utils/sendEmailWithTemplate.js - Message processor → Template email sender: sends notifications
utils/sendEmailWithTemplate.js - MongoDB connection → MongoDB: connects to
- Email and file queries → MongoDB: reads and writes
- Template email sender → Receiver and sender templates: renders
utils/emailService.js - Template email sender → SMTP service: sends mail