SNS notification types (email, SMS, Lambda) in AWS - Time & Space Complexity

Time Complexity: SNS notification types (email, SMS, Lambda)

O(n)

Understanding Time Complexity

When sending notifications using SNS with different types like email, SMS, and Lambda, it's important to know how the number of notifications affects the work done.

We want to understand how the time to send notifications grows as we increase the number of messages.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

# Create SNS topic
aws sns create-topic --name MyTopic

# Subscribe email, SMS, and Lambda endpoints
aws sns subscribe --topic-arn arn:aws:sns:region:account:MyTopic --protocol email --notification-endpoint [e-mail]
aws sns subscribe --topic-arn arn:aws:sns:region:account:MyTopic --protocol sms --notification-endpoint [phone]
aws sns subscribe --topic-arn arn:aws:sns:region:account:MyTopic --protocol lambda --notification-endpoint arn:aws:lambda:region:account:function:MyFunction

# Publish message to topic
aws sns publish --topic-arn arn:aws:sns:region:account:MyTopic --message "Hello Subscribers"
    

This sequence sets up a topic with three types of subscribers and sends one message to all.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Publishing a message to the SNS topic.
• How many times: Once per message, but SNS fans out to all subscribers.
• Dominant operation: SNS sending notifications to each subscriber endpoint (email, SMS, Lambda).

How Execution Grows With Input

Each message sent to the topic triggers SNS to send notifications to all subscribers.

Input Size (n subscribers)	Approx. Notifications Sent
10	10 notifications
100	100 notifications
1000	1000 notifications

Pattern observation: The number of notifications grows directly with the number of subscribers.

Final Time Complexity

Time Complexity: O(n)

This means the time to send notifications grows linearly with the number of subscribers.

Common Mistake

[X] Wrong: "Sending one message to SNS means only one notification is sent regardless of subscribers."

[OK] Correct: SNS fans out the message to every subscriber, so the total notifications equal the number of subscribers.

Interview Connect

Understanding how SNS scales with subscribers helps you design systems that handle many users efficiently and shows you can reason about cloud service behavior.

Self-Check

"What if we added message filtering so only some subscribers get notified? How would the time complexity change?"

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