Why SNS notification types (email, SMS, Lambda) in AWS? - Purpose & Use Cases

The Big Idea

What if one simple message could instantly reach all your customers in different ways without extra effort?

The Scenario

Imagine you have to tell your friends about an event by sending separate emails, text messages, and calling them one by one. You write each message yourself and use different apps for each type. It takes a lot of time and you might forget someone.

The Problem

Doing this manually is slow and tiring. You can make mistakes like sending the wrong message or missing a person. Also, if you want to add a new way to notify, you have to learn a new tool and repeat the process. It's easy to get overwhelmed and confused.

The Solution

Using SNS notification types lets you send messages to many people at once through email, SMS, or even trigger a Lambda function automatically. You set it up once, and SNS handles sending the right message to the right place without extra work from you.

Before vs After

✗ Before

Send email via app A
Send SMS via app B
Call function manually

✓ After

Publish message to SNS topic
SNS sends email, SMS, triggers Lambda automatically

What It Enables

You can notify many people and systems instantly and reliably with one simple action.

Real Life Example

A company wants to alert customers about a sale by email and SMS, and also update their website automatically. SNS sends emails and texts while Lambda updates the site, all triggered by one message.

Key Takeaways

Manual notifications are slow and error-prone.

SNS sends messages via email, SMS, and Lambda automatically.

This saves time and ensures everyone gets the right message fast.

Practice

1. Which of the following is NOT a valid protocol for an AWS SNS subscription?

easy

A. email

B. sms

C. lambda

D. ftp

Solution

1. Step 1: Review SNS supported protocols

   AWS SNS supports protocols like email, sms, and lambda for subscriptions.

2. Step 2: Identify unsupported protocol

   FTP is not supported as a protocol for SNS subscriptions.

3. Final Answer:

   ftp -> Option D

4. Quick Check:

   Supported protocols exclude ftp [OK]

Hint: Remember SNS supports email, sms, lambda but not ftp [OK]

Common Mistakes:

• Confusing FTP as supported protocol
• Thinking HTTP is the only protocol
• Mixing SNS with S3 protocols

2. Which is the correct way to specify an SMS subscription protocol in AWS SNS?

easy

A. Protocol: 'sms', Endpoint: '[e-mail]'

B. Protocol: 'email', Endpoint: '[phone]'

C. Protocol: 'sms', Endpoint: '[phone]'

D. Protocol: 'lambda', Endpoint: '[phone]'

Solution

1. Step 1: Understand protocol and endpoint types

   For SMS, protocol must be 'sms' and endpoint is a phone number with country code.

2. Step 2: Match correct protocol and endpoint

   Protocol: 'sms', Endpoint: '[phone]' correctly uses 'sms' protocol and a phone number endpoint.

3. Final Answer:

   Protocol: 'sms', Endpoint: '[phone]' -> Option C

4. Quick Check:

   SMS needs phone number endpoint [OK]

Hint: SMS protocol requires phone number endpoint format [OK]

Common Mistakes:

• Using email as protocol for SMS
• Using email address as SMS endpoint
• Using lambda protocol with phone number

3. Given this AWS SNS subscription code snippet:

sns.subscribe({
  Protocol: 'lambda',
  Endpoint: 'arn:aws:lambda:us-east-1:123456789012:function:ProcessMessage'
});

What happens when a message is published to this SNS topic?

medium

A. The Lambda function 'ProcessMessage' is invoked with the message payload.

B. The message is sent as an SMS to the Lambda function ARN.

C. The message is sent as an email to the Lambda function.

D. The subscription will fail because Lambda cannot be an endpoint.

Solution

1. Step 1: Identify protocol and endpoint meaning

   Protocol 'lambda' means SNS invokes the specified Lambda function ARN when a message is published.

2. Step 2: Understand message delivery behavior

   The Lambda function 'ProcessMessage' is called with the message payload as input.

3. Final Answer:

   The Lambda function 'ProcessMessage' is invoked with the message payload. -> Option A

4. Quick Check:

   Lambda protocol triggers function invocation [OK]

Hint: Lambda protocol triggers function call, not email or SMS [OK]

Common Mistakes:

• Thinking Lambda receives email or SMS
• Assuming subscription fails
• Confusing endpoint ARN with phone/email

4. You created an SNS subscription with protocol 'email' but the subscriber never receives messages. What is the most likely cause?

medium

A. The email address was not confirmed by the subscriber.

B. The SNS topic does not support email protocol.

C. The subscription endpoint was set to a phone number.

D. Lambda function is not attached to the subscription.

Solution

1. Step 1: Understand email subscription confirmation

   Email subscriptions require the recipient to confirm by clicking a link in a confirmation email.

2. Step 2: Identify common cause of no delivery

   If the email is not confirmed, SNS will not send notifications to that address.

3. Final Answer:

   The email address was not confirmed by the subscriber. -> Option A

4. Quick Check:

   Email subscriptions need confirmation [OK]

Hint: Email subscriptions require confirmation before delivery [OK]

Common Mistakes:

• Assuming SNS does not support email
• Confusing phone number as email endpoint
• Expecting Lambda involvement in email subscription

5. You want to send an SMS notification and also trigger a Lambda function whenever a message is published to an SNS topic. How should you configure the subscriptions?

hard

A. Create one subscription with protocol 'email' and endpoint as phone number, and another with protocol 'lambda' and endpoint as Lambda ARN.

B. Create one subscription with protocol 'sms' and endpoint as phone number, and another with protocol 'lambda' and endpoint as Lambda ARN.

C. Create one subscription with protocol 'lambda' and endpoint as phone number, and another with protocol 'sms' and endpoint as Lambda ARN.

D. Create one subscription with protocol 'sms' and endpoint as Lambda ARN, and another with protocol 'lambda' and endpoint as phone number.

Solution

1. Step 1: Understand protocol and endpoint matching

   SMS protocol requires a phone number endpoint; Lambda protocol requires Lambda function ARN.

2. Step 2: Configure two subscriptions correctly

   Create one subscription with protocol 'sms' and phone number endpoint, and another with protocol 'lambda' and Lambda ARN endpoint.

3. Final Answer:

   Create one subscription with protocol 'sms' and endpoint as phone number, and another with protocol 'lambda' and endpoint as Lambda ARN. -> Option B

4. Quick Check:

   Match protocol to correct endpoint type [OK]

Hint: Match SMS to phone number, Lambda to function ARN [OK]

Common Mistakes:

• Mixing endpoints and protocols
• Using email protocol for SMS
• Assigning Lambda ARN as SMS endpoint