Other AWS Service Categories (Task 3.8)

Other In-Scope AWS Service Categories

Source: https://docs.aws.amazon.com/whitepapers/latest/aws-overview/aws-services.html

This topic covers the "long tail" the exam references. You need the ONE-LINE PURPOSE of each — and for the integration trio (SQS/SNS/EventBridge), the mechanics, because decoupling questions go deeper here than anywhere else in CLF.

Application Integration — the Decoupling Trio

SQS — the buffer

How it works: producers PUT messages to the queue; workers PULL them. Once a worker receives a message it becomes invisible for the visibility timeout (default 30 s) — if the worker dies, the message REAPPEARS for another worker (no loss). Standard queues are at-least-once (rare duplicates); FIFO queues are exactly-once with strict ordering within message groups. A dead-letter queue captures messages that fail repeatedly (maxReceiveCount) for debugging. Long polling (up to 20 s) waits for messages instead of returning empty — cheaper and near-real-time.

Real use-case: Black Friday orders overwhelm the fulfillment system: the web tier enqueues 40k orders/min to SQS; workers process 8k/min steadily behind the buffer. Nobody is dropped, nothing crashes — the queue absorbs the spike (that is what "decouple" means in money terms).

SNS — the fan-out

How it works: publishers send ONE message to a TOPIC; every subscriber (email, SMS, mobile push, Lambda, SQS, HTTP endpoints) receives a copy. Adding a consumer = subscribing it — zero producer changes.

Real use-case: an order event must update the warehouse, email the customer, and feed analytics: publish once to SNS; three SQS queues subscribe, each processed independently at its own pace. Adding fraud-check as a 4th consumer is a subscription, not a code deploy — the SNS→SQS fan-out pattern.

EventBridge — the router

How it works: a managed event bus where RULES match event patterns (JSON) and route to targets: "orders over $1,000 → fraud Lambda," "any state change → archive to S3." AWS services emit events natively, and SaaS sources (Zendesk, PagerDuty, Shopify) can too; scheduled rules replace cron.

Real use-case: "When an EC2 instance state changes to stopped outside business hours, alert the on-call" — one EventBridge rule with a pattern, no code polling anything.

Gotchas & interview notes: buffer under load, one message one processor → SQS; push the same event to many systems → SNS; route by content, SaaS/AWS-native events, cron → EventBridge; orchestrate multi-step with retries → Step Functions. The trio composes: SNS fan-out into SQS queues (durable, independently paced) is the canonical answer to "fan out AND buffer."

Business Applications

• Amazon Simple Email Service (SES): transactional/marketing email from applications (order confirmations, password resets).
• Amazon Connect: cloud contact center — phone/chat for help desks, omni-channel routing, pay-as-you-go.
• AWS Activate for Startups: credits, support, training for startups.
• AWS IQ: hire AWS-certified freelancers for quick projects.
• AWS Managed Services (AMS): AWS operates your infrastructure for you (enterprise).
• AWS Support: plans (Basic/Developer/Business/Enterprise — see the Billing domain topic).
• Amazon WorkSpaces: managed VDI — full virtual Windows/Linux desktops for employees.
• Amazon AppStream 2.0: stream a single application to any device.
• Amazon WorkSpaces Web: browser-based secure desktop access.
• AWS Amplify: framework + hosting for web/mobile frontends with ready backends (auth, APIs, storage).
• AWS AppSync: managed GraphQL API with realtime subscriptions.
• AWS IoT Core: connect billions of devices to AWS (MQTT messaging, per-device certificates/auth).
• AWS IoT Greengrass: run Lambda + ML on the device itself (at the edge), syncing with the cloud.
• "Send an order-confirmation email from the app" → SES
• "Call center in the cloud" → Connect
• "Run compiled CI tests on every push" → CodeBuild
• "Debug which microservice is slow" → X-Ray
• "Ship a React app with auth and an API fast" → Amplify
• "Stream a CAD app to tablets" → AppStream 2.0
• "Collect sensor data from 50,000 factory devices" → IoT Core
• "Process messages one at a time from a queue" → SQS

Customer Engagement / Expert Help

• Amazon Simple Email Service (SES): transactional/marketing email from applications (order confirmations, password resets).
• Amazon Connect: cloud contact center — phone/chat for help desks, omni-channel routing, pay-as-you-go.
• AWS Activate for Startups: credits, support, training for startups.
• AWS IQ: hire AWS-certified freelancers for quick projects.
• AWS Managed Services (AMS): AWS operates your infrastructure for you (enterprise).
• AWS Support: plans (Basic/Developer/Business/Enterprise — see the Billing domain topic).
• Amazon WorkSpaces: managed VDI — full virtual Windows/Linux desktops for employees.
• Amazon AppStream 2.0: stream a single application to any device.
• Amazon WorkSpaces Web: browser-based secure desktop access.
• AWS Amplify: framework + hosting for web/mobile frontends with ready backends (auth, APIs, storage).
• AWS AppSync: managed GraphQL API with realtime subscriptions.
• AWS IoT Core: connect billions of devices to AWS (MQTT messaging, per-device certificates/auth).
• AWS IoT Greengrass: run Lambda + ML on the device itself (at the edge), syncing with the cloud.
• "Send an order-confirmation email from the app" → SES
• "Call center in the cloud" → Connect
• "Run compiled CI tests on every push" → CodeBuild
• "Debug which microservice is slow" → X-Ray
• "Ship a React app with auth and an API fast" → Amplify
• "Stream a CAD app to tablets" → AppStream 2.0
• "Collect sensor data from 50,000 factory devices" → IoT Core
• "Process messages one at a time from a queue" → SQS

Developer Tools (CI/CD and Coding)

The pipeline story: commit to CodeCommit → CodePipeline triggers CodeBuild (test) → CodeDeploy ships to EC2/ECS/Lambda → X-Ray traces requests in production. Each stage is replaceable and the whole chain is itself infrastructure-as-code.

Real use-case: A latency complaint arrives: X-Ray's service map shows 480 ms of the 600 ms response spent in one downstream call to the pricing service — the "which microservice is slow" question answered with a trace, not a war room.

End-User Computing

• Amazon Simple Email Service (SES): transactional/marketing email from applications (order confirmations, password resets).
• Amazon Connect: cloud contact center — phone/chat for help desks, omni-channel routing, pay-as-you-go.
• AWS Activate for Startups: credits, support, training for startups.
• AWS IQ: hire AWS-certified freelancers for quick projects.
• AWS Managed Services (AMS): AWS operates your infrastructure for you (enterprise).
• AWS Support: plans (Basic/Developer/Business/Enterprise — see the Billing domain topic).
• Amazon WorkSpaces: managed VDI — full virtual Windows/Linux desktops for employees.
• Amazon AppStream 2.0: stream a single application to any device.
• Amazon WorkSpaces Web: browser-based secure desktop access.
• AWS Amplify: framework + hosting for web/mobile frontends with ready backends (auth, APIs, storage).
• AWS AppSync: managed GraphQL API with realtime subscriptions.
• AWS IoT Core: connect billions of devices to AWS (MQTT messaging, per-device certificates/auth).
• AWS IoT Greengrass: run Lambda + ML on the device itself (at the edge), syncing with the cloud.
• "Send an order-confirmation email from the app" → SES
• "Call center in the cloud" → Connect
• "Run compiled CI tests on every push" → CodeBuild
• "Debug which microservice is slow" → X-Ray
• "Ship a React app with auth and an API fast" → Amplify
• "Stream a CAD app to tablets" → AppStream 2.0
• "Collect sensor data from 50,000 factory devices" → IoT Core
• "Process messages one at a time from a queue" → SQS

Example: contractors need Photoshop but should not install it locally → AppStream 2.0 streams the app; full remote-desktop employees → WorkSpaces. The distinction: WorkSpaces gives a DESKTOP, AppStream gives an APP.

Frontend Web and Mobile

• Amazon Simple Email Service (SES): transactional/marketing email from applications (order confirmations, password resets).
• Amazon Connect: cloud contact center — phone/chat for help desks, omni-channel routing, pay-as-you-go.
• AWS Activate for Startups: credits, support, training for startups.
• AWS IQ: hire AWS-certified freelancers for quick projects.
• AWS Managed Services (AMS): AWS operates your infrastructure for you (enterprise).
• AWS Support: plans (Basic/Developer/Business/Enterprise — see the Billing domain topic).
• Amazon WorkSpaces: managed VDI — full virtual Windows/Linux desktops for employees.
• Amazon AppStream 2.0: stream a single application to any device.
• Amazon WorkSpaces Web: browser-based secure desktop access.
• AWS Amplify: framework + hosting for web/mobile frontends with ready backends (auth, APIs, storage).
• AWS AppSync: managed GraphQL API with realtime subscriptions.
• AWS IoT Core: connect billions of devices to AWS (MQTT messaging, per-device certificates/auth).
• AWS IoT Greengrass: run Lambda + ML on the device itself (at the edge), syncing with the cloud.
• "Send an order-confirmation email from the app" → SES
• "Call center in the cloud" → Connect
• "Run compiled CI tests on every push" → CodeBuild
• "Debug which microservice is slow" → X-Ray
• "Ship a React app with auth and an API fast" → Amplify
• "Stream a CAD app to tablets" → AppStream 2.0
• "Collect sensor data from 50,000 factory devices" → IoT Core
• "Process messages one at a time from a queue" → SQS

Real use-case: a hackathon team ships a React app with sign-in, an API, and file uploads in an afternoon using Amplify — the backend pieces are provisioned from config, not code marathons.

IoT

• Amazon Simple Email Service (SES): transactional/marketing email from applications (order confirmations, password resets).
• Amazon Connect: cloud contact center — phone/chat for help desks, omni-channel routing, pay-as-you-go.
• AWS Activate for Startups: credits, support, training for startups.
• AWS IQ: hire AWS-certified freelancers for quick projects.
• AWS Managed Services (AMS): AWS operates your infrastructure for you (enterprise).
• AWS Support: plans (Basic/Developer/Business/Enterprise — see the Billing domain topic).
• Amazon WorkSpaces: managed VDI — full virtual Windows/Linux desktops for employees.
• Amazon AppStream 2.0: stream a single application to any device.
• Amazon WorkSpaces Web: browser-based secure desktop access.
• AWS Amplify: framework + hosting for web/mobile frontends with ready backends (auth, APIs, storage).
• AWS AppSync: managed GraphQL API with realtime subscriptions.
• AWS IoT Core: connect billions of devices to AWS (MQTT messaging, per-device certificates/auth).
• AWS IoT Greengrass: run Lambda + ML on the device itself (at the edge), syncing with the cloud.
• "Send an order-confirmation email from the app" → SES
• "Call center in the cloud" → Connect
• "Run compiled CI tests on every push" → CodeBuild
• "Debug which microservice is slow" → X-Ray
• "Ship a React app with auth and an API fast" → Amplify
• "Stream a CAD app to tablets" → AppStream 2.0
• "Collect sensor data from 50,000 factory devices" → IoT Core
• "Process messages one at a time from a queue" → SQS

Real use-case: 50,000 factory sensors publish temperature over MQTT to IoT Core; rules route readings over thresholds to SNS for maintenance alerts, while Greengrass on the local gateway runs the anomaly model offline when the plant's internet drops.

Worked Example: Choosing by Scenario

• Amazon Simple Email Service (SES): transactional/marketing email from applications (order confirmations, password resets).
• Amazon Connect: cloud contact center — phone/chat for help desks, omni-channel routing, pay-as-you-go.
• AWS Activate for Startups: credits, support, training for startups.
• AWS IQ: hire AWS-certified freelancers for quick projects.
• AWS Managed Services (AMS): AWS operates your infrastructure for you (enterprise).
• AWS Support: plans (Basic/Developer/Business/Enterprise — see the Billing domain topic).
• Amazon WorkSpaces: managed VDI — full virtual Windows/Linux desktops for employees.
• Amazon AppStream 2.0: stream a single application to any device.
• Amazon WorkSpaces Web: browser-based secure desktop access.
• AWS Amplify: framework + hosting for web/mobile frontends with ready backends (auth, APIs, storage).
• AWS AppSync: managed GraphQL API with realtime subscriptions.
• AWS IoT Core: connect billions of devices to AWS (MQTT messaging, per-device certificates/auth).
• AWS IoT Greengrass: run Lambda + ML on the device itself (at the edge), syncing with the cloud.
• "Send an order-confirmation email from the app" → SES
• "Call center in the cloud" → Connect
• "Run compiled CI tests on every push" → CodeBuild
• "Debug which microservice is slow" → X-Ray
• "Ship a React app with auth and an API fast" → Amplify
• "Stream a CAD app to tablets" → AppStream 2.0
• "Collect sensor data from 50,000 factory devices" → IoT Core
• "Process messages one at a time from a queue" → SQS