[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"lesson-aws-certified-cloud-practitioner-cloud-technology-and-services-other-aws-services-application-integration-en":4,"next-aws-certified-cloud-practitioner-cloud-technology-and-services-other-aws-services-application-integration-en":300,"prev-aws-certified-cloud-practitioner-cloud-technology-and-services-other-aws-services-application-integration-en":310},null,{"locked":5,"reason":3,"meta":6,"item":17},false,{"title":7,"description":8,"isFree":9,"estimatedMinutes":10,"difficulty":11,"learningObjectives":12},"Application Integration Services","Learn the AWS application integration services that connect decoupled components: Amazon SQS for message queues, Amazon SNS for pub/sub fan-out, Amazon EventBridge for event routing, and AWS Step Functions for workflow orchestration.",true,16,"beginner",[13,14,15,16],"Explain why application integration services help you build decoupled, event-driven systems","Describe what Amazon SQS, Amazon SNS, Amazon EventBridge, and AWS Step Functions each do","Compare a message queue (SQS) with a pub/sub topic (SNS)","Match a described integration need to the right AWS service",{"id":18,"title":7,"body":19,"description":8,"difficulty":11,"estimatedMinutes":10,"extension":225,"infographics":226,"isFree":9,"learningObjectives":246,"meta":247,"navigation":9,"path":248,"quiz":249,"seo":297,"stem":298,"__hash__":299},"courses/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/08-other-aws-services/01-application-integration.md",{"type":20,"value":21,"toc":213},"minimark",[22,27,31,34,39,43,46,49,52,69,72,76,79,82,86,89,92,96,99,102,105,109,112,115,118,122,189,193],[23,24,26],"h2",{"id":25},"why-this-matters","Why this matters",[28,29,30],"p",{},"A modern application is rarely one program. It is many small parts that hand work to each other: a web layer takes an order, another component charges the card, a third updates inventory, and a fourth sends an email. If those parts call each other directly, one slow or failed component can freeze the whole system.",[28,32,33],{},"Application integration services solve this. They let the parts of an application talk to each other without being tightly connected, which is called decoupling. The components pass messages or events through a managed service instead of calling each other directly, so one part can fail, slow down, or scale up on its own without breaking the rest. The CLF-C02 exam tests 4 of these services at a recognition level: Amazon SQS, Amazon SNS, Amazon EventBridge, and AWS Step Functions. Your job is to match a described need to the right one.",[35,36],"infographic",{"alt":37,"slug":38},"A comparison of the four AWS application integration services: Amazon SQS as a message queue, Amazon SNS as a pub/sub topic, Amazon EventBridge as a rule-based event bus, and AWS Step Functions as a step-by-step workflow.","messaging-services-comparison",[23,40,42],{"id":41},"amazon-sqs-message-queues","Amazon SQS: message queues",[28,44,45],{},"Amazon Simple Queue Service (Amazon SQS) is a fully managed message queue. A producer puts messages into the queue, and a consumer pulls them out to process one at a time, at its own pace. The queue stores the messages in between, so the producer and consumer never have to be available at the same moment.",[28,47,48],{},"This is the classic way to decouple a fast front end from slower back-end work. Imagine a website that accepts photo uploads. Instead of making the user wait while each photo is resized, the site drops a message in an SQS queue and responds right away. A separate worker reads the queue and resizes the photos when it can. If the worker falls behind or restarts, the messages wait safely in the queue.",[28,50,51],{},"SQS offers 2 queue types you should recognize by name:",[53,54,55,63],"ul",{},[56,57,58,62],"li",{},[59,60,61],"strong",{},"Standard queues"," give maximum throughput and at-least-once delivery, with best-effort ordering.",[56,64,65,68],{},[59,66,67],{},"FIFO queues"," (first-in, first-out) guarantee that messages are processed exactly once, in the exact order they were sent.",[28,70,71],{},"Think of SQS as point-to-point: each message is meant for one consumer to handle.",[23,73,75],{"id":74},"amazon-sns-pubsub-fan-out","Amazon SNS: pub/sub fan-out",[28,77,78],{},"Amazon Simple Notification Service (Amazon SNS) is a managed publish/subscribe (pub/sub) messaging service. Publishers send messages to a topic, and the topic pushes a copy of each message to every subscriber. This is many-to-many, or fan-out: one message reaches many destinations at once.",[28,80,81],{},"Subscribers can be SQS queues, AWS Lambda functions, HTTP/S endpoints, and even end users through SMS, email, and mobile push. So SNS is the service to reach for when a single event needs to trigger several reactions in parallel, or when you need to send notifications to people.",[35,83],{"alt":84,"slug":85},"A fan-out diagram showing a publisher sending one message to an Amazon SNS topic, which delivers copies in parallel to two SQS queues and a Lambda function.","sns-sqs-fanout",[28,87,88],{},"A very common design is SNS plus SQS together. The publisher sends one message to an SNS topic, and the topic delivers it to several SQS queues. Each queue feeds a different consumer, so billing, shipping, and analytics can all react to the same order event without knowing about each other.",[28,90,91],{},"The fastest way to tell SNS and SQS apart: SQS is a queue that one consumer pulls from, while SNS pushes each message to many subscribers.",[23,93,95],{"id":94},"amazon-eventbridge-the-event-bus","Amazon EventBridge: the event bus",[28,97,98],{},"Amazon EventBridge is a serverless event bus. An event bus receives a stream of events and routes each one to the right place based on rules you define. A rule matches events by their content, then sends matching events to one or more targets, such as a Lambda function, an SQS queue, or Step Functions.",[28,100,101],{},"What sets EventBridge apart is where the events come from. It can receive events from your own applications, from many AWS services, and from third-party SaaS applications like Zendesk or Shopify. That makes it the natural choice for building event-driven systems that react to activity across tools you do not control.",[28,103,104],{},"A simple way to hold the distinction: SNS broadcasts a message to its subscribers, while EventBridge inspects each event and routes it by rules, including events from SaaS partners.",[23,106,108],{"id":107},"aws-step-functions-orchestrating-workflows","AWS Step Functions: orchestrating workflows",[28,110,111],{},"The first 3 services move individual messages or events. AWS Step Functions is different: it coordinates a whole sequence of steps as a single workflow.",[28,113,114],{},"You define the steps as a visual workflow (a state machine), and Step Functions runs them in order, passes data from one step to the next, retries steps that fail, and tracks the state of the entire process. This is orchestration. It fits any multi-step job where order and error handling matter, such as processing an order, running a data pipeline, or approving a request.",[28,116,117],{},"Picture an order workflow: validate the payment, then reserve inventory, then send a confirmation. If reserving inventory fails, Step Functions can retry it or branch to a different path, all without you writing the plumbing to track where the process is.",[23,119,121],{"id":120},"putting-them-side-by-side","Putting them side by side",[123,124,125,141],"table",{},[126,127,128],"thead",{},[129,130,131,135,138],"tr",{},[132,133,134],"th",{},"Service",[132,136,137],{},"What it is",[132,139,140],{},"Reach for it when",[142,143,144,156,167,178],"tbody",{},[129,145,146,150,153],{},[147,148,149],"td",{},"Amazon SQS",[147,151,152],{},"Managed message queue (pull-based)",[147,154,155],{},"You need to decouple components and let one consumer process messages at its own pace",[129,157,158,161,164],{},[147,159,160],{},"Amazon SNS",[147,162,163],{},"Pub/sub messaging (push-based)",[147,165,166],{},"One message must fan out to many subscribers, or you need to notify people by SMS, email, or push",[129,168,169,172,175],{},[147,170,171],{},"Amazon EventBridge",[147,173,174],{},"Serverless event bus",[147,176,177],{},"You need to route events by rules, especially from AWS services or SaaS apps",[129,179,180,183,186],{},[147,181,182],{},"AWS Step Functions",[147,184,185],{},"Workflow orchestration",[147,187,188],{},"You need to run a multi-step process in order, with retries and error handling",[23,190,192],{"id":191},"exam-tips","Exam tips",[53,194,195,198,201,204,207,210],{},[56,196,197],{},"Application integration services exist to decouple the parts of an application so they can fail and scale independently.",[56,199,200],{},"Amazon SQS is a message queue. One consumer pulls each message. Standard queues favor throughput, FIFO queues guarantee order and exactly-once processing.",[56,202,203],{},"Amazon SNS is pub/sub. It fans out one message to many subscribers (SQS queues, Lambda, HTTP, SMS, email, push). SNS plus SQS is the classic fan-out pattern.",[56,205,206],{},"Tell SQS and SNS apart: SQS is a queue one consumer reads, SNS pushes to many subscribers at once.",[56,208,209],{},"Amazon EventBridge is a serverless event bus that routes events by rules and can ingest events from SaaS applications.",[56,211,212],{},"AWS Step Functions orchestrates multi-step workflows with built-in ordering, retries, and error handling. Pick it when a scenario describes coordinating several steps.",{"title":214,"searchDepth":215,"depth":215,"links":216},"",3,[217,219,220,221,222,223,224],{"id":25,"depth":218,"text":26},2,{"id":41,"depth":218,"text":42},{"id":74,"depth":218,"text":75},{"id":94,"depth":218,"text":95},{"id":107,"depth":218,"text":108},{"id":120,"depth":218,"text":121},{"id":191,"depth":218,"text":192},"md",[227,236],{"slug":38,"concept":228,"style":229,"aspectRatio":230,"labels":231},"Four contrasting message topologies side by side, one per integration service. Amazon SQS shows a queue that a single consumer pulls from at its own pace; Amazon SNS shows one message pushed to many subscribers at once; Amazon EventBridge shows a bus whose rules route each event to the right target; AWS Step Functions shows an ordered chain of steps with retries built in. The orange accent marks the fan-out point of the SNS topic, the sharpest visual contrast with the one-consumer queue beside it. Takeaway: pick the service by how the message needs to move, not by the message itself.","comparison","16:9",[232,233,234,235],"SQS: queue, one consumer pulls","SNS: one message pushed to many","EventBridge: rules route each event","Step Functions: ordered steps with retries",{"slug":85,"concept":237,"style":238,"aspectRatio":230,"labels":239},"A one-to-many fan-out showing a publisher sending a single message to an Amazon SNS topic, which copies it in parallel to every subscriber: an SQS queue feeding a billing consumer, another SQS queue feeding a shipping consumer, and a Lambda function reacting to the same event. All branches leave the topic at the same moment to show parallel delivery, with no subscriber aware of the others. The orange accent sits on the SNS topic at the center of the fan, the point where one message becomes many. Takeaway: publish once, and every system that cares gets its own copy to process independently.","diagram",[240,241,242,243,244,245],"Publisher sends one message","SNS topic copies to every subscriber","SQS queue: billing consumer","SQS queue: shipping consumer","Lambda reacts to the same event","All subscribers process in parallel",[13,14,15,16],{},"/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/08-other-aws-services/01-application-integration",{"passingScore":250,"questions":251},70,[252,261,265,273,278,283,289],{"question":253,"type":254,"options":255,"correctAnswer":257,"explanation":260},"What problem do AWS application integration services like Amazon SQS and Amazon SNS solve?","single",[256,257,258,259],"They store large files cheaply for long-term archiving","They let the parts of an application communicate without being tightly connected, so one component can fail or scale without breaking the others","They encrypt data at rest inside a database","They provide virtual desktops to remote employees","Application integration services decouple components, so a slow or failed part does not bring down the rest of the system. Archiving is Amazon S3 Glacier, encryption at rest is handled by services like AWS KMS, and virtual desktops are Amazon WorkSpaces.",{"question":262,"type":254,"options":263,"correctAnswer":149,"explanation":264},"Which AWS service is a fully managed message queue used to decouple components, where a producer sends messages that one consumer pulls and processes?",[160,149,182,171],"Amazon SQS is a message queue: a producer puts messages in, and a consumer pulls them out to process at its own pace. SNS is pub/sub fan-out, Step Functions orchestrates workflows, and EventBridge routes events.",{"question":266,"type":254,"options":267,"correctAnswer":268,"explanation":272},"What is the key difference between Amazon SQS and Amazon SNS?",[268,269,270,271],"SQS is a queue where one consumer pulls each message, while SNS is pub/sub where one message is pushed to many subscribers at once","SQS is for email and SNS is for SMS only","SQS runs on-premises while SNS runs in the cloud","There is no difference; they are the same service","SQS is a pull-based queue for point-to-point work, where each message is processed by one consumer. SNS is push-based pub/sub, where a single message fans out to many subscribers in parallel.",{"question":274,"type":254,"options":275,"correctAnswer":182,"explanation":277},"A team needs to coordinate a multi-step order process: validate payment, then reserve inventory, then send a confirmation, with automatic retries if a step fails. Which service is built for this?",[149,160,182,276],"Amazon S3","AWS Step Functions coordinates a sequence of steps as a visual workflow and handles ordering, retries, and error handling for you. SQS and SNS move individual messages but do not orchestrate a multi-step process.",{"question":279,"type":254,"options":280,"correctAnswer":171,"explanation":282},"Which AWS service is a serverless event bus that uses rules to route events from your applications, AWS services, and SaaS apps to targets like AWS Lambda?",[171,149,182,281],"Amazon Connect","Amazon EventBridge is a serverless event bus that matches events against rules and routes them to targets, and it can receive events from SaaS applications. SQS is a queue, Step Functions is a workflow service, and Connect is a contact center.",{"question":284,"type":254,"options":285,"correctAnswer":286,"explanation":288},"Amazon SNS can fan out a single published message to multiple subscribers at the same time, such as several SQS queues and a Lambda function.",[286,287],"True","False","A common pattern is SNS fan-out: a publisher sends one message to an SNS topic, and the topic delivers a copy to every subscriber in parallel, including SQS queues, Lambda functions, and HTTP endpoints. This lets several systems react to the same event independently.",{"question":290,"type":291,"options":292,"correctAnswers":295,"explanation":296},"Which two AWS services are most often used together so that one event can be delivered to several queues for parallel processing? (Select all that apply.)","multiple",[160,149,293,294],"AWS X-Ray","Amazon WorkSpaces",[160,149],"In the fan-out pattern, an SNS topic delivers each message to multiple SQS queues so different consumers can process the same event in parallel. X-Ray is for debugging and WorkSpaces is a virtual desktop service.",{"title":7,"description":8},"courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/08-other-aws-services/01-application-integration","j7DUaU5UZPkScr3rZEkqUB91-nFvh0EUr9c4toO9_AE",{"locked":9,"reason":301,"meta":302,"item":3},"paywall",{"title":303,"description":304,"isFree":5,"estimatedMinutes":10,"difficulty":11,"learningObjectives":305},"AWS Developer Tools","Learn the AWS developer tools that automate building, testing, and releasing software: AWS CodePipeline, CodeBuild, CodeDeploy, and CodeArtifact for CI/CD, plus AWS X-Ray for debugging and CloudShell for a browser-based shell.",[306,307,308,309],"Explain what continuous integration and continuous delivery (CI/CD) mean","Describe the role of AWS CodePipeline, CodeBuild, CodeDeploy, and CodeArtifact in a release pipeline","Identify AWS X-Ray as the service for analyzing and debugging distributed applications","Recognize the AWS developer environments: AWS CloudShell and Amazon Q Developer",{"locked":9,"reason":301,"meta":311,"item":3},{"title":312,"description":313,"isFree":5,"estimatedMinutes":314,"difficulty":11,"learningObjectives":315},"AWS Analytics Services","Learn the core AWS analytics services: Amazon Athena, Redshift, EMR, AWS Glue, Amazon Kinesis and Data Firehose, QuickSight, Lake Formation, OpenSearch Service, and how they fit into a data pipeline.",18,[316,317,318,319],"Describe the stages of a typical AWS analytics pipeline: ingest, store, process, query, and visualize","Match the core analytics services to the job each one does","Compare Amazon Athena, Amazon Redshift, and Amazon EMR","Identify which services handle real-time streaming data"]