Cloud Technology and Services
Integration, Business, Developer, End-User, and IoT Services
ImportantRecognize messaging, business application, developer, end-user computing, frontend, support, and IoT services by the problem each solves.
Aligned to the current CLF-C02 exam guide, verified August 15, 2026.
Why this matters
This task covers several smaller categories. Good preparation means recognizing the primary purpose and the most important neighboring-service distinctions.
Must Know
- Amazon SQS buffers messages in a durable queue so producers and consumers can work independently. Amazon SNS pushes one published message to multiple subscribers. Amazon EventBridge routes matching events from AWS, SaaS, or custom sources to targets.
- AWS Step Functions coordinates steps and state in a workflow; it is not a general message queue.
- Amazon Connect provides a cloud contact center. Amazon SES sends and receives email for applications and organizations.
- AWS CodeBuild builds and tests code, AWS CodePipeline automates delivery stages, and AWS X-Ray traces requests through distributed applications.
- Amazon WorkSpaces provides virtual desktops. WorkSpaces Applications is the current name for Amazon AppStream 2.0 application streaming. WorkSpaces Secure Browser provides managed secure browser access.
- AWS Amplify supports development and deployment of web and mobile application frontends. AWS IoT Core connects devices with cloud applications and other services.
- AWS Support provides plan-dependent technical assistance and Support Center cases. Support-plan details are freshness-sensitive and are taught in depth in the billing and support domain.
Compare and Distinguish
- SQS vs SNS: SQS buffers work for consumers to pull; SNS pushes messages to multiple subscribers.
- SNS vs EventBridge: SNS emphasizes publish/subscribe fanout; EventBridge applies event patterns and routes matching events to targets.
- EventBridge vs Step Functions: EventBridge routes events; Step Functions orchestrates ordered workflow steps and state.
- Connect vs SES: Connect is a customer contact center; SES is an email service.
- CodeBuild vs CodePipeline vs X-Ray: build/test, delivery workflow, and distributed request tracing are different jobs.
- WorkSpaces vs WorkSpaces Applications vs Secure Browser: full virtual desktop, streamed applications, and managed browser access.
- AWS Support vs self-service resources: Support offers plan-dependent cases and assistance; documentation and re:Post provide self-service knowledge.
Scenario examples
- Scenario: An order service must keep work until a separate processor is ready. Think: Amazon SQS provides a queue.
- Scenario: One alert must reach email, SMS, and multiple application subscribers. Think: Amazon SNS provides fanout.
- Scenario: Events from several AWS services must be routed to targets according to matching rules. Think: Amazon EventBridge.
- Scenario: Employees need complete managed virtual desktops. Think: Amazon WorkSpaces.
- Scenario: Connected devices must exchange messages securely with cloud applications. Think: AWS IoT Core.
Exam traps
- Amazon SES sends email but is not a queue or an event bus.
- Step Functions coordinates a workflow; it does not replace SQS as a durable work buffer.
- A streamed application is not the same experience as a full persistent virtual desktop.
- Do not memorize obsolete Support plan response-time tables; use the current support material and recognize names retained by the exam guide.
Key takeaways
- Queue: SQS. Fanout: SNS. Event rules: EventBridge. Workflow: Step Functions.
- Contact center: Connect. Email: SES.
- Build: CodeBuild. Delivery stages: CodePipeline. Trace: X-Ray.
- Desktop: WorkSpaces. Streamed app: WorkSpaces Applications/AppStream 2.0. Secure browser: WorkSpaces Secure Browser.
- Frontend/mobile: Amplify. Connected devices: IoT Core.
How it works
- A producer sends to an SQS queue, publishes to an SNS topic, or emits an event that EventBridge evaluates against rules.
- Developer tools act at different delivery stages: CodeBuild executes builds, CodePipeline coordinates stages, and X-Ray collects trace data.
- End-user computing services stream either a desktop, an application, or a browser experience to the user.
When to use it
- Use SQS to buffer, SNS to fan out, EventBridge to route events, and Step Functions to coordinate workflow steps.
- Use Connect for contact centers and SES for application email.
- Use the developer, end-user, frontend, or IoT service whose primary outcome exactly matches the scenario.
- Use AWS Support when direct AWS assistance is needed and the applicable plan provides the required capability.
Security and governance implications
- Authorize producers, consumers, publishers, subscribers, and event targets separately using least privilege.
- Device identity, message authorization, and data protection remain important even when AWS manages the IoT service.
- Virtual delivery changes the presentation layer; it does not remove application and data-access controls.
Troubleshooting signals
- For missing messages, identify the pattern first: queue polling, topic subscription delivery, or event-rule matching.
- For developer tools, locate the failing stage—build, pipeline coordination, or runtime request—before selecting the service.
- For end-user services, clarify whether the user needs a desktop, one application, or a controlled browser.
More detail
- Decoupling lets a producer submit work without requiring the consumer to process it immediately. A queue preserves work until a consumer retrieves it; fanout and event routing solve different delivery patterns.
- WorkSpaces Applications is the current product name for the application-streaming service still named Amazon AppStream 2.0 in the live exam guide. Recognize both names without treating the rename date as trivia.
- AWS IoT Core supports device connectivity, message exchange, authentication, and rules that can send messages to supported AWS targets.
Ready for the quiz?
- Would a producer that must wait for a consumer use SNS or SQS?
- How does EventBridge differ from Step Functions?
- Which developer tool traces a request across services?
- Can you distinguish a virtual desktop, streamed application, and secure browser?
- Which service provides device-to-cloud messaging?
Related objectives
- D3.8