1
00:00:06,550 --> 00:00:10,410
- Now let's review the
Amazon Simple Email Service.

2
00:00:10,410 --> 00:00:12,190
With Amazon Simple Email Service,

3
00:00:12,190 --> 00:00:13,520
or SES,

4
00:00:13,520 --> 00:00:16,270
we get a service that is ideal

5
00:00:16,270 --> 00:00:19,270
for sending bulk emails at scale,

6
00:00:19,270 --> 00:00:22,490
so think about sending tens of thousands,

7
00:00:22,490 --> 00:00:23,570
hundreds of thousands,

8
00:00:23,570 --> 00:00:25,360
or maybe even millions of emails

9
00:00:25,360 --> 00:00:28,360
to potentially millions of customers

10
00:00:28,360 --> 00:00:31,560
and not only sending those emails,

11
00:00:31,560 --> 00:00:34,030
but ensuring that they get delivered

12
00:00:34,030 --> 00:00:37,080
and tracking the results of that campaign,

13
00:00:37,080 --> 00:00:40,340
and so Simple Email
Service helps eliminate

14
00:00:40,340 --> 00:00:43,430
the complexities of delivering email.

15
00:00:43,430 --> 00:00:45,780
If you've ever tried
to do this on your own

16
00:00:45,780 --> 00:00:47,860
outside of a service like SES,

17
00:00:47,860 --> 00:00:50,460
then you may have come to figure out

18
00:00:50,460 --> 00:00:53,220
that it's one thing to send an email.

19
00:00:53,220 --> 00:00:55,860
It's another thing to
ensure that those emails

20
00:00:55,860 --> 00:00:58,150
actually reach the inbox.

21
00:00:58,150 --> 00:01:01,550
Doing that is a very complex process,

22
00:01:01,550 --> 00:01:06,410
mainly due to validation
of the actual address

23
00:01:06,410 --> 00:01:08,420
and ensuring that they get through

24
00:01:08,420 --> 00:01:11,920
various spam filters through
the chain of delivery.

25
00:01:11,920 --> 00:01:13,030
And so,

26
00:01:13,030 --> 00:01:16,820
Simple Email Service
takes over the burdens

27
00:01:16,820 --> 00:01:18,760
of those complexities
so that we don't have

28
00:01:18,760 --> 00:01:20,802
to worry about it and so,

29
00:01:20,802 --> 00:01:24,280
we can use Simple Email Service to send

30
00:01:24,280 --> 00:01:26,470
all kinds of different types of emails.

31
00:01:26,470 --> 00:01:29,490
We may send transactional emails,

32
00:01:29,490 --> 00:01:31,990
so emails that are essentially a receipt

33
00:01:31,990 --> 00:01:33,520
of a particular action,

34
00:01:33,520 --> 00:01:37,440
so a user signs up and then
we send them a welcome email.

35
00:01:37,440 --> 00:01:41,850
A user forgets their password
and we send them a reset link.

36
00:01:41,850 --> 00:01:45,123
The user purchases something
and we send them a receipt,

37
00:01:46,380 --> 00:01:48,270
or we can send marketing emails

38
00:01:48,270 --> 00:01:51,960
where we may target a particular segment

39
00:01:51,960 --> 00:01:55,760
of our user base and send
a particular campaign

40
00:01:55,760 --> 00:02:00,040
to that group of customers
or we may send emails

41
00:02:00,040 --> 00:02:03,690
to every customer and in that regard,

42
00:02:03,690 --> 00:02:07,150
we're sending potentially
upwards of millions of emails

43
00:02:07,150 --> 00:02:09,290
at one time.

44
00:02:09,290 --> 00:02:13,360
We might also have social
networking types of emails,

45
00:02:13,360 --> 00:02:18,360
so a user invites their
friends to do something

46
00:02:18,770 --> 00:02:21,980
and so you send out emails to maybe

47
00:02:21,980 --> 00:02:26,343
a small group of people based
on the actions of one person.

48
00:02:27,640 --> 00:02:29,090
Whatever the case may be,

49
00:02:29,090 --> 00:02:32,150
the idea here is that we're sending email

50
00:02:32,150 --> 00:02:36,320
and we want to ensure that the
email actually gets delivered

51
00:02:36,320 --> 00:02:41,320
and we want to track the
status of that delivery,

52
00:02:42,670 --> 00:02:45,020
and so we're gonna talk about
that here in just a minute.

53
00:02:45,020 --> 00:02:49,020
And so, we can send these
emails with an API call.

54
00:02:49,020 --> 00:02:53,130
We can send many, many
emails with one API call.

55
00:02:53,130 --> 00:02:56,490
We can also use SMTP if we wanted to.

56
00:02:56,490 --> 00:02:59,820
It just depends on how you
want to write your software,

57
00:02:59,820 --> 00:03:01,870
the software that is
actually sending the email.

58
00:03:01,870 --> 00:03:03,620
That's totally up to you.

59
00:03:03,620 --> 00:03:05,690
We also get a sandbox environment

60
00:03:05,690 --> 00:03:10,660
so that we can develop
against an email service

61
00:03:10,660 --> 00:03:13,100
without actually sending
millions of emails

62
00:03:13,100 --> 00:03:14,193
to real people.

63
00:03:15,074 --> 00:03:18,270
Now, like I mentioned earlier,

64
00:03:18,270 --> 00:03:21,410
we can also track the delivery status,

65
00:03:21,410 --> 00:03:25,450
so we would want to know how many emails

66
00:03:25,450 --> 00:03:27,240
actually made it to the inbox,

67
00:03:27,240 --> 00:03:29,360
how many emails were opened,

68
00:03:29,360 --> 00:03:31,470
how many were marked as spam,

69
00:03:31,470 --> 00:03:35,234
how many bounced because of a bad address,

70
00:03:35,234 --> 00:03:38,120
or how many were deleted.

71
00:03:38,120 --> 00:03:41,540
All of that kind of information
is automatically collected

72
00:03:41,540 --> 00:03:46,190
and made available to us by
the Simple Email Service.

73
00:03:46,190 --> 00:03:49,130
We can also use Simple Email Service

74
00:03:49,130 --> 00:03:51,980
to receive incoming mail.

75
00:03:51,980 --> 00:03:56,980
This is very helpful for
handling email programmatically.

76
00:03:57,080 --> 00:04:01,950
If you want to enable
your users to email images

77
00:04:01,950 --> 00:04:04,430
or email particular pieces of data,

78
00:04:04,430 --> 00:04:06,320
then we can set up Simple Email Service

79
00:04:06,320 --> 00:04:10,710
to receive that incoming mail
and we can have that delivered

80
00:04:10,710 --> 00:04:15,710
to an S3 bucket and then we
can also automatically invoke

81
00:04:16,610 --> 00:04:21,610
Lambda functions to do some
type of an automated processing

82
00:04:22,740 --> 00:04:23,763
of that email.

83
00:04:25,680 --> 00:04:27,970
Now, when we're using this service,

84
00:04:27,970 --> 00:04:32,313
it's really important to
be aware of sending limits.

85
00:04:33,290 --> 00:04:37,230
Sending limits are really
put in place to help

86
00:04:37,230 --> 00:04:40,790
ensure that your email
doesn't get caught up

87
00:04:40,790 --> 00:04:41,760
in spam filters.

88
00:04:41,760 --> 00:04:46,490
If we start sending a
barrage of email immediately,

89
00:04:46,490 --> 00:04:47,953
right out of the gate,

90
00:04:50,290 --> 00:04:51,790
downstream services,

91
00:04:51,790 --> 00:04:55,370
ISPs and email providers
could end up flagging

92
00:04:55,370 --> 00:04:58,940
our entire domain as a source of spam

93
00:04:58,940 --> 00:05:00,930
and so we have a number of limits

94
00:05:00,930 --> 00:05:03,580
that you should be aware
of and I will refer you

95
00:05:03,580 --> 00:05:06,040
to the documentation for
the specific numbers,

96
00:05:06,040 --> 00:05:08,780
but several of them would be first,

97
00:05:08,780 --> 00:05:10,270
a sending quota.

98
00:05:10,270 --> 00:05:13,710
So, we do have the
maximum number of emails

99
00:05:13,710 --> 00:05:18,270
that we are allowed to
send in a 24 hour period.

100
00:05:18,270 --> 00:05:20,950
We also have the send rate,

101
00:05:20,950 --> 00:05:22,420
which is the number of emails

102
00:05:22,420 --> 00:05:24,720
that we are sending per second.

103
00:05:24,720 --> 00:05:27,560
And those limits,

104
00:05:27,560 --> 00:05:29,720
when we first set up Simple Email Service

105
00:05:29,720 --> 00:05:31,330
for a particular domain,

106
00:05:31,330 --> 00:05:33,970
those limits are set fairly low

107
00:05:33,970 --> 00:05:34,803
and so again,

108
00:05:36,746 --> 00:05:38,750
it's not necessarily for Amazon.

109
00:05:38,750 --> 00:05:43,210
Amazon has the ability to
send just about any volume.

110
00:05:43,210 --> 00:05:47,540
This is really to help us
sort of get under the radar

111
00:05:47,540 --> 00:05:52,020
of the recipient's
email provider, so again

112
00:05:52,020 --> 00:05:56,330
we want to avoid just this
massive barrage of emails

113
00:05:56,330 --> 00:05:59,000
and then being flagged as a spam source,

114
00:05:59,000 --> 00:06:04,000
and so by starting at
a lower rate of emails,

115
00:06:04,740 --> 00:06:08,880
once those systems begin to trust

116
00:06:08,880 --> 00:06:11,200
that we are sending quality email,

117
00:06:11,200 --> 00:06:15,180
then those limits will be
automatically lifted over time.

118
00:06:15,180 --> 00:06:16,870
So again, it is up to you.

119
00:06:16,870 --> 00:06:19,200
It is your responsibility to ensure

120
00:06:19,200 --> 00:06:22,623
that you are adhering to these limits

121
00:06:26,000 --> 00:06:30,240
and that trusting that over time,

122
00:06:30,240 --> 00:06:32,130
as you send quality email,

123
00:06:32,130 --> 00:06:33,870
those limits will be lifted.

124
00:06:33,870 --> 00:06:38,870
So, if you have a need to
send transactional emails,

125
00:06:38,930 --> 00:06:41,653
to send bulk emails for
marketing campaigns,

126
00:06:43,060 --> 00:06:44,220
social networking emails,

127
00:06:44,220 --> 00:06:48,440
any kind of thing that
requires you to send an email

128
00:06:48,440 --> 00:06:50,760
and you need to ensure that its delivered

129
00:06:50,760 --> 00:06:52,720
and then track the status,

130
00:06:52,720 --> 00:06:55,503
then take a look at Amazon's
Simple Email Service.