Curriculum Overview: AWS Application Integration Services

This curriculum covers the core AWS services designed to enable communication between independent components of cloud-native applications: Amazon EventBridge, Amazon Simple Notification Service (SNS), and Amazon Simple Queue Service (SQS). These services are fundamental to building decoupled, highly scalable, and event-driven architectures.

## Prerequisites

Before starting this module, students should possess the following foundational knowledge:

• Cloud Fundamentals: Basic understanding of AWS Regions, Availability Zones, and the Shared Responsibility Model.
• Computing Basics: Familiarity with Amazon EC2 (instances) and AWS Lambda (serverless functions).
• Data Formats: A basic understanding of JSON (JavaScript Object Notation), as it is the primary format for events and messages.
• Architectural Concepts: Awareness of the difference between monolithic and microservices architectures.

## Module Breakdown

## Module Objectives per Module

Module 1: Amazon EventBridge

• Define EventBridge as a "smart hub" for application events.
• Configure Rules to trigger actions based on system state changes (e.g., an EC2 instance stopping).
• Differentiate between event-based triggers and metric-based triggers (CloudWatch Alarms).

Module 2: Amazon SNS

• Explain the Publish/Subscribe (Pub/Sub) model.
• Identify supported protocols: SMS, Email, HTTP/S, and Lambda.
• Understand the "fan-out" pattern where one message is sent to multiple subscribers.

Module 3: Amazon SQS

• Define Decoupling and its importance in preventing system failure cascades.
• Distinguish between Standard Queues (at-least-once delivery) and FIFO Queues (first-in-first-out).
• Describe how SQS acts as a buffer to handle spikes in traffic.

## Visual Anchors

Service Selection Logic

Integration Architecture Example

## Success Metrics

To demonstrate mastery of this curriculum, the student must be able to:

• Identify which service to use when a requirement specifies "pushing notifications to mobile devices" (SNS).
• Explain how SQS prevents a web server from crashing during a sudden burst of 1,000,000 requests.
• Design a simple workflow where EventBridge triggers a Lambda function based on an IAM user login event.
• Calculate basic free tier limits: Recognize that SNS and SQS both offer ~1 million free requests/publishes.

## Real-World Application

In a career as a Cloud Architect or Developer, these services are the "glue" of the cloud:

• Resilience: By using SQS, you ensure that if your database goes down, your messages aren't lost—they stay in the queue until the database returns.
• Agility: With EventBridge, you can add new features (like an email alert) to an existing system without modifying the original code; you simply add a new event rule.
• Scalability: These services are serverless and scale automatically, meaning you don't have to manage servers for your messaging infrastructure.

## Examples Section

[!TIP] Use these scenarios to decide which service to implement in your architecture.

▶Deep Dive: SNS vs. SQS

While both handle messages, remember: SNS is Push (it sends data to you immediately) and SQS is Pull (your application must go and ask for the data). They are often used together in a "Fan-out" pattern where SNS sends a message to multiple SQS queues simultaneously.