3.7 Application Integration and Other Services
Key Takeaways
- Amazon SQS (Simple Queue Service) is a fully managed message queuing service for decoupling application components.
- Amazon SNS (Simple Notification Service) is a pub/sub messaging service for sending notifications to multiple subscribers.
- Amazon EventBridge is a serverless event bus for building event-driven architectures by routing events between AWS services and applications.
- AWS Step Functions orchestrate multiple AWS services into serverless workflows with visual workflow design.
- Amazon API Gateway creates, publishes, and manages REST and WebSocket APIs at any scale.
Quick Answer: Application-integration services let components communicate without tight dependencies. SQS is a pull-based message queue (one consumer per message), SNS is push-based pub/sub (every subscriber gets the message), EventBridge is a serverless event bus, Step Functions orchestrates workflows, and API Gateway fronts APIs. Together they enable the loosely coupled, resilient architectures AWS favors.
Messaging and Event Services
Amazon SQS (Simple Queue Service)
Amazon SQS is a fully managed message queue that decouples and scales microservices and distributed systems.
| Feature | Detail |
|---|---|
| Type | Pull-based message queue |
| Retention | 1 minute to 14 days (default 4 days) |
| Max Message Size | 256 KB |
| Queue Types | Standard (best-effort order, at-least-once) and FIFO (exact order, exactly-once) |
| Scaling | Virtually unlimited throughput |
| Use Case | Decoupling, buffering requests, task queues |
Example: an ordering front end drops orders into an SQS queue; worker instances process them at their own pace, so a traffic spike fills the queue instead of overwhelming the workers.
Amazon SNS (Simple Notification Service)
Amazon SNS is a pub/sub service that pushes one message to many subscribers at once.
| Feature | Detail |
|---|---|
| Type | Push-based pub/sub |
| Subscribers | SQS, Lambda, HTTP/HTTPS, email, SMS, mobile push |
| Topics | Named channels that fan out to all subscribers |
| Filtering | Policies route messages to specific subscribers |
| Use Case | Fan-out notifications, alerting, event-driven workflows |
SQS vs. SNS
| Feature | SQS (Queue) | SNS (Pub/Sub) |
|---|---|---|
| Model | Pull — consumers poll | Push — delivered to subscribers |
| Delivery | One consumer processes each message | All subscribers receive every message |
| Use Case | Decoupling, task queues | Fan-out notifications |
| Persistence | Messages retained until processed | Deliver-and-forget |
On the Exam: SQS = one consumer per message (a queue). SNS = every subscriber gets it (broadcast). A classic combined pattern is SNS fan-out to multiple SQS queues, where one event triggers several independent processing pipelines.
Amazon EventBridge
Amazon EventBridge is a serverless event bus for event-driven architectures. Rules match incoming events and route them to targets; a schema registry discovers event structures; it also connects to SaaS partners. It was formerly CloudWatch Events.
Example: when an EC2 instance changes state, an EventBridge rule triggers a Lambda function to send a notification.
Workflow Orchestration
AWS Step Functions
Step Functions coordinates multiple AWS services into serverless workflows defined as state machines, with a visual designer plus branching, parallel execution, retries, and error handling. Use it for order processing, data pipelines, human-approval steps, and ML pipelines.
API Management
Amazon API Gateway
API Gateway creates, publishes, and manages REST, HTTP, and WebSocket APIs at any scale, with throttling, caching, API keys, and authorization built in. The canonical serverless backend is API Gateway + Lambda, with both scaling automatically and no servers to manage.
Developer, IoT, and End-User Services
| Service | Purpose |
|---|---|
| AWS Amplify | Full-stack web/mobile development platform |
| AWS AppSync | Managed GraphQL API service |
| AWS Device Farm | Test apps on real devices |
| AWS IoT Core | Connect and manage IoT devices at scale |
| AWS IoT Greengrass | Run compute, messaging, and ML at the edge |
| Amazon WorkSpaces | Managed virtual desktops (DaaS) |
| Amazon AppStream 2.0 | Stream desktop applications to any device |
Migration, Marketplace, and Other Services
| Service | Purpose |
|---|---|
| AWS Migration Hub | Track migration progress centrally |
| AWS Application Migration Service | Automate lift-and-shift server migration |
| AWS Database Migration Service (DMS) | Migrate databases with minimal downtime |
| AWS Transfer Family | SFTP/FTPS/FTP transfers into S3 |
| Amazon Connect | Cloud contact center |
| AWS Marketplace | Catalog of third-party software (AMIs, SaaS, containers, data) |
| AWS Service Catalog | Curate approved internal IT services |
| AWS License Manager | Track and enforce software licenses |
On the Exam: Watch the difference between AWS Marketplace (buy third-party/AWS software) and AWS Service Catalog (publish your own approved products internally). Both are "catalogs," but for opposite audiences.
Why Decoupling Matters
The reason these services appear so often is that AWS architecture strongly favors loose coupling. When components call each other directly, a slowdown or failure in one cascades into the others, and you cannot scale or update pieces independently. Inserting a queue (SQS), a topic (SNS), or an event bus (EventBridge) between components breaks that chain: a failed consumer simply leaves messages in the queue until it recovers, and each side scales on its own.
This pattern maps directly to the Reliability and Performance Efficiency pillars of the Well-Architected Framework. Expect "decouple the components" scenarios where the right answer is SQS, SNS, or EventBridge rather than a direct, synchronous connection. A buffering queue in front of a processing tier is also the standard way to absorb sudden traffic spikes without dropping work.
One more distinction worth memorizing: SQS and SNS handle messages, while Step Functions handles workflows and EventBridge handles events. If a scenario describes coordinating an ordered, multi-step process with branching and retries, the answer is Step Functions, not a raw queue. If it describes reacting to a state change emitted by an AWS service or SaaS app, the answer is EventBridge. Reading for "message," "event," or "multi-step workflow" usually selects the right service on the first pass.
What is the key difference between Amazon SQS and Amazon SNS?
A company wants to build a serverless REST API backend. Which combination of services should they use?
Which AWS service provides a serverless event bus for routing events between AWS services and applications?
Which service coordinates multiple AWS services into serverless workflows using visual state machines?
Which AWS service provides managed virtual desktops that allow users to access a Windows or Linux desktop from any supported device?
A company needs to migrate their on-premises Oracle database to Amazon Aurora PostgreSQL. Which AWS service can convert the database schema?
Which AWS service provides a digital catalog where customers can find, buy, and deploy third-party software?
Which service provides a fully managed ETL (Extract, Transform, Load) capability for preparing data for analytics?
A company wants to create interactive business intelligence dashboards from their data. Which AWS service should they use?
Which AWS service would you use to translate text from English to Spanish in real time?
A company wants to extract text and data from scanned invoices and receipts. Which AWS AI service is BEST suited?