How to use AWS SES with Lambda in Ruby on Rails application - Michał Łęcicki
Download as PPTX, PDF0 likes86 views
The document outlines the transition from a legacy Ruby on Rails application for email management to using AWS SES with Lambda for improved email handling. It highlights the benefits of the new solution, including better scalability, easier configuration, and effective processing of incoming emails using AWS services. Challenges during the implementation include local setup difficulties and managing logs, but the new system offers a cloud-friendly and extendable architecture.
How to use AWS SES with Lambda in Ruby on Rails application - Michał Łęcicki
- 1. How to use AWS SES with Lambda in Ruby on Rails application Michał Łęcicki
- 2. Background • Ruby on Rails application with legacy code • Many dependent services: Postfix, Sidekiq, Sphinx, Mysql • One dedicated server • No documentation
- 3. Emails - from user perspective • Sending & receiving emails in application • Approximately 20 000 email daily • Different types of emails: • communications • data imports
- 4. Emails - from system perspective
- 5. Old solution flaws • No cloud friendly • Outdated libraries, difficult configuration • Problems with deployments • No monitoring & hard debugging • No backup
- 6. Alternatives • Fetch emails directly with IMAP protocol • Third-party tools • Rails Action Mailbox • AWS SES (Simple Email Service)
- 7. AWS Simple Email Service • Simple configuration • Compatible with other AWS services • Cost effective • Easy to check -> prototype created in 3 days
- 8. New solution
- 9. New approach Receiver • Email receiving (SES) • Storing email messages (S3) • Notifying about new emails (Lambda) Feeder • Check for new emails (Sidekiq) • Processing new emails (Rails)
- 11. AWS Lambda • Invoked every time new item is added to S3 bucket • Create new entry in email_requests table t.string "email_type" t.string "s3_file_link", null: false t.string "lambda_request_id", null: false t.datetime “started_processing_at" t.datetime "finished_processing_at"
- 12. AWS Lambda gotchas • Local setup & development • Logs are quite troublesome • Be aware of duplicates! • Unintuitive setup of versions & aliases • Hard to save in terraform
- 13. New solution • Cloudy • Very extendable • Complex setup, but within one provider • Saving & storing emails is independent from processing them
- 14. Thank you for your attention!