Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/roxsross/aws-cloud-practitioner-complete-guide/llms.txt

Use this file to discover all available pages before exploring further.

Beyond the core compute, storage, networking, and database layers, AWS provides a rich ecosystem of services that help you connect application components, add intelligence to your workloads, automate deployments, and gain operational visibility. This page covers the four supporting categories most frequently tested in the CLF-C02 exam: application integration, AI and machine learning, developer and DevOps tools, and management and monitoring.

Application Integration Services

Modern cloud architectures rely on loosely coupled, asynchronous communication between components. AWS provides a set of managed messaging and orchestration services that let you build resilient, scalable, event-driven applications without managing the underlying messaging infrastructure.
Amazon SQS is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. Producers write messages to a queue; consumers poll the queue and process messages independently.

Queue Types

TypeBehaviorBest For
Standard QueueAt-least-once delivery, best-effort orderingMaximum throughput; order not critical
FIFO QueueExactly-once processing, strict orderingFinancial transactions, order processing

Key Concepts

  • Visibility Timeout — Time a message is hidden from other consumers after being received (prevents duplicate processing)
  • Dead-Letter Queue (DLQ) — Captures messages that fail processing after a configurable number of retries
  • Message retention — Up to 14 days
  • Max message size — 256 KB
SQS is the foundational service for decoupling producers from consumers — if the downstream service is slow or temporarily unavailable, messages queue up safely rather than causing upstream failures.
Amazon SNS is a fully managed pub/sub (publish-subscribe) messaging service. A publisher sends one message to an SNS topic, and SNS fans that message out to all subscribed endpoints simultaneously.

Supported Subscription Protocols

  • SQS queues (fan out to queues for further processing)
  • Lambda functions
  • HTTP/HTTPS endpoints
  • Email and Email-JSON
  • SMS text messages
  • Mobile push notifications (APNs, FCM, ADM)

Fan-Out Pattern

A common architecture combines SNS with SQS: publish one event to an SNS topic and fan out to multiple SQS queues. Each queue is processed independently — enabling parallel processing pipelines from a single event source.
Amazon EventBridge is a serverless event bus that connects AWS services, SaaS applications, and your own custom applications using events. It routes events based on rules that you define, enabling event-driven architectures without custom integration code.

Key Concepts

  • Event Bus — Receives events from sources (default AWS bus, custom buses, SaaS partner buses)
  • Rules — Match incoming events and route them to one or more targets
  • Targets — Lambda, SQS, SNS, Step Functions, EC2 Run Command, Kinesis, and more
  • Schema Registry — Automatically discovers and documents event schemas
EventBridge is the evolution of Amazon CloudWatch Events and is the recommended service for building event-driven integrations between AWS services and third-party SaaS applications.
AWS Step Functions is a serverless workflow orchestration service that lets you coordinate multiple AWS services into serverless workflows using visual state machines. Each step in the workflow is a state; Step Functions manages retries, error handling, branching, and parallel execution automatically.

Use Cases

  • Order fulfillment pipelines
  • Data processing and ETL workflows
  • Machine learning model training pipelines
  • Microservice orchestration with conditional logic

Workflow Types

  • Standard Workflows — Long-running (up to 1 year), exactly-once execution, full audit history
  • Express Workflows — High-volume, short-duration (up to 5 min), at-least-once execution
Amazon API Gateway is a fully managed service that makes it easy to create, publish, maintain, monitor, and secure REST, HTTP, and WebSocket APIs at any scale. It acts as the “front door” for applications to access data, business logic, or functionality from your backend services.

Key Features

  • Request throttling — Protect backends from traffic spikes
  • Authorization — Integrate with AWS IAM, Amazon Cognito, or custom Lambda authorizers
  • API Keys — Control and meter access to your APIs
  • Caching — Cache API responses to reduce backend load and improve latency
  • WebSocket APIs — Two-way communication for real-time applications (chat, dashboards)
API Gateway is most commonly paired with Lambda to build fully serverless REST APIs — no EC2 instances required.

Key Service Relationships at a Glance

SQS vs SNS

SQS is a pull-based queue — one consumer processes each message. SNS is push-based pub/sub — one message fans out to all subscribers simultaneously. They are often combined in the fan-out pattern.

CloudWatch vs CloudTrail

CloudWatch monitors operational metrics and logs (what is happening). CloudTrail records API activity (who did what, when). Use CloudTrail for security audits and compliance; use CloudWatch for performance monitoring and alerting.

CloudFormation vs CDK

CloudFormation uses JSON/YAML templates for infrastructure as code. CDK uses programming languages (Python, TypeScript, etc.) and compiles down to CloudFormation. CDK offers higher-level abstractions; CloudFormation is the underlying engine.

Trusted Advisor vs Well-Architected

Trusted Advisor gives real-time, automated checks against AWS best practices. Well-Architected Tool guides structured architectural reviews against the six Well-Architected pillars — more strategic and workload-specific.
SQS vs SNS — the exam’s favorite distinction:
  • SQS decouples a producer from a consumer — messages wait in the queue until pulled. Perfect when you need to buffer requests or level out traffic spikes.
  • SNS fans out one message to many subscribers at once — email, SMS, Lambda, and SQS queues can all receive the same notification simultaneously.
  • When you see both used together, it is the classic fan-out pattern: SNS publishes → multiple SQS queues subscribe → independent consumers process in parallel.
Monitoring vs auditing — never confuse these two:
  • Amazon CloudWatch → Performance metrics, application logs, resource utilization, alarms, dashboards
  • AWS CloudTrail → API call history, user activity, who deleted that S3 bucket, which IAM user changed a security group
  • If a question asks “how do you know who made a change in your AWS account?” — the answer is CloudTrail, every time.

Build docs developers (and LLMs) love