Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SVC103 The Whys and Hows of Integrating Amazon Simple Email Service into your Product or Website - AWS re: Invent 2012

2,120 views

Published on

If you're already building your website our application on AWS, using Amazon SES is a quick and cost-effective way to send your email. This session will talk about what Amazon SES is and why you would want to use it. Then we will dig into the most common ways our customers use Amazon SES with their current systems and give you the tools you need to do the same.

  • Be the first to comment

  • Be the first to like this

SVC103 The Whys and Hows of Integrating Amazon Simple Email Service into your Product or Website - AWS re: Invent 2012

  1. 1. #reinvent
  2. 2. Why is sending email hard?DNS settings Deliverability Sender IDIP seasoning Complaints Feedback loopsDKIM Bounces ...and more!Special servers (MTAs) Content filtersISP throttling IP reputationRecipient response Domain reputationSpam SPF
  3. 3. Is your email important?Up to 183 billion spam messages aresent daily. Don’t become a casualty!
  4. 4. • Email sending service• Pay as you go with no long-term commitments• Robust sending platform• No email infrastructure headache• Quickly scale your sending
  5. 5. 01101000 01101001 Sender Amazon SES Receiver ISP
  6. 6. 01101000 01101001 Sender Amazon SES Receiver ISP
  7. 7. 01101000 01101001 Sender Amazon SES Receiver ISP
  8. 8. Features• SMTP or API• Bounces and complaints via Amazon Simple Notification Service (Amazon SNS)• Mailbox Simulator• Easy DKIM• Domain Verification (Amazon Route 53 optional “easy button”)
  9. 9. AOL’s Spam definition and Email Sender best practices
  10. 10. AOL
  11. 11. Billions BlockedBlocked Spam of Daily Spam+ Spam Folder Inbound Delivery 88% Email 91% Delivered to Inbox Based on September 2012 metrics
  12. 12. AOL’s definition of spam• Spam = Mail that users do not want• Simple annoyances (ex. pharmaceuticals, stock picks, etc…)• Subscribed mail that the user no longer wants• Received due to a previous relationship (ex. deal or sale messages from a vendor)• Malicious attempt to obtain personal information or credentials• Malicious intent from downloaded software
  13. 13. Spam Complaint AOL Feedback Loop Data Anti-Spam System IPs, URLs,Domains, etc. Spam Complaint Feedback Loop IPs, URLs, Data Domains, etc. IPs, URLs, Centralized Domains, etc. Other Major External Mail Service Data Services Providers IPs, URLs, Domains, etc.
  14. 14. • Send email from a consistent, identifiable email address• When users subscribe, tell them what to expect and how often they will receive email from you• Mail should be branded and easily identifiable by the recipient• Setup feedback loops and use the results to: • Remove spam complainers from the mailing list • Learn what type of mail users mark as spam to inform your future sending• Honor "unsubscribe" requests, and detail how to unsubscribe in an easy to find place (maybe the message footer)• Setup SPF for ALL IPs from which mail is sent• Sign ALL mail using DKIM• Adopt usage of DMARC feedback loops and policy enforcement
  15. 15. AWS SES followsAOL’s email senderbest practices
  16. 16. SMTP or HTTPSUsers Application Amazon SES Feedback
  17. 17. SMTP or HTTPSUsers Application Amazon SES Feedback
  18. 18. http://aws.amazon.com/ses/https://aws.amazon.com/documentationhttps://forums.aws.amazon.comhttp://sesblog.amazon.comhttp://aws.amazon.com/whitepapers/
  19. 19. We are sincerely eager to hear your feedback on thispresentation and on re:Invent. Please fill out an evaluation form when you have a chance. #reinvent

×