ExamFinch.com My Study

Study guide

3.7 Application Integration and Other Services

Practice this exam

AWS Certified Cloud Practitioner CLF-C02

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Cloud Practitioner (CLF-C02) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (24%)

1.1 What Is Cloud Computing? 1.2 Cloud Deployment Models 1.3 AWS Well-Architected Framework 1.4 Cloud Migration Strategies 1.5 Cloud Economics

3 Domain 2: Security and Compliance (30%)

2.1 The AWS Shared Responsibility Model 2.2 AWS Identity and Access Management (IAM) 2.3 AWS Security Services 2.4 Compliance and Governance 2.5 Network Security

4 Domain 3: Cloud Technology and Services (34%)

3.1 AWS Compute Services 3.2 AWS Storage Services 3.3 AWS Database Services 3.4 AWS Networking and Content Delivery 3.5 Management and Governance Services 3.6 AI/ML and Analytics Services 3.7 Application Integration and Other Services

5 Domain 4: Billing, Pricing, and Support (12%)

4.1 AWS Pricing Models 4.2 Billing and Cost Management Tools 4.3 AWS Support Plans 4.4 Additional Billing Concepts and Services

6 AWS Services Deep Dive

5.1 Compute Services Deep Dive 5.2 Storage and Database Deep Dive 5.3 Security Services Deep Dive 5.4 Architecture Best Practices and Design Principles 5.5 Practice Exam — Mixed Domain Questions

3.7 Application Integration and Other Services

Key Takeaways Explain This Topic AI

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.

Last updated: October 2026

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 1 MiB (1,048,576 bytes)
  • 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 (now Amazon WorkSpaces Applications) 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.