WGU-D282 - AWS Cloud Foundations - App Integration complete questions with expert solutions + rationales

F-M serverless real-time streamed event bus to build event-driven apps at scale using events generated from apps and services

AWS EventBridge

Systems integration using decoupled architecture to simplify integration and architecture efforts as well as future-proofing

EventBridge biz impact

Re-arc using decoupling, ops monitoring, SaaS integration, integration with AI/ML

EventBridge use cases

use declarative rules to couple source to sink across a durable event-based service bus architecture

EventBridge routing rules

Configured integration originators of events for intended downstream processing by configured targets within a given event bus workflow

EventBridge Source

A structured packet of data representing an indication of change within the event bus system

EventBridge Event

Routes source to target and can only be attached to ONE bus.

EventBridge Rule

Eventual receiver of event for processing which can be configured services or HTTPS endpoints

EventBridge Target

real-time event processor applying particular rules to route from source to target.

Event Bus

receives events from configured AWS services

Default Event Bus

Process events from a different account/region

Eventbridge - Custom Event Bus

used to process events from 3P apps (SaaS, services)

EventBridge partner Event Bus

Link a px source to a px event bus

EventBridge partner event source

Alter event content or format prior to sending to a configured target

EventBridge Input Transformer

Save events to support verification or replay workflows

EventBridge Archive

Event structure definitions supporting all AWS services and custom schemas in a schema registry

EventBridge Schema/Registry/Discovery

Downloadable schema and bus configuration allowing IDEs to interact with the EventBridge API for dev/test, and troubleshooting

EventBridge Code Bindings

use identity and resource based policies to control access to event bus workflow and components

EventBridge AWS IAM RBAC support

F-M message queuing service at scale

AWS SQS

Simplifies architecture, decoupling to reduce dependency and support operation (and failure) to be independent at any message volume, reducing dedicated messaging infra need.

AWS SQS biz impact

M-que with Hi-thruput ALO delivery with no guaranteed order, cost effective

SQS Standard Queue

M-que with Lower thruput, EO delivery, strict order, slighty higher cost

SQS FIFO Queue

Structured packet of information or instruction for intended downstream processing

SQS Message

Configured message originator

SQS Producer

Configured eventual message processor

SQS Consumer

M-que does not forward, therefore consumers need to request over API for next messages to process

SQS Polling

M-Q returns immediate response with msg or no msg (empty response)

SQS Short polling

Consumer sends M-Q request and then waits for a configured interval (up to 20s) for response - reducing # of empty responses.

SQS Long Polling

Configured time where message is visible to consumers on the queue designed to prevent multiple consumers from processing the same message

SQS Visibility timeout

After visibility timeout, if processed successfully, the message is...

Deleted by SQS

Message routed to optional M-Q if not successfully processed after a configured number of retry operations, often to support analysis and debugging efforts.

SQS Dead-letter Queue (DLQ)

send messages to multiple A-Zs or regions

SQS distributed resiliency

Based on type of M-Q, # of requests, data transfer, retention, and message timers, plus any DLQ config

SQS Pricing

F-M messaging pub/sub thread messaging and notification service

AWS SNS

Decouples architecture, providing async communication to distributed services, reducing complexity and improving scale

AWS SNS biz impact

Workflows like user engagement, alerts, mobile, event-driven

SNS use cases

A structured packet of information intended for downstream processing

SNS Message

SNS Topic

Default, ALO, no guaranteed order, fastest topic type

Standard Topic

EO, strict order - used where msg sequence and integrity are critical

FIFO Topic

Message originator creating and sending message to a particular topic for intended downstream processing by a subscriber

SNS Publisher

Message processor configured to a particular topic, and can have multiple subscriptions to same or different topics

SNS Subscriber

Optional M-Q storing messages from topics that cannot be processed by subscribers aiding in analysis and troubleshooting

SNS DLQ

SNS can stretch and shrink to meet demand.

SNS scale and elasticity

Price varies by region, delivery destination, data transfer, msg size, optional features

SNS Pricing

What is the key differentiating factor between SQS, SNS, and Kinesis?

SQS - msg Q for async comms, SNS for pub/sub, email/SMS notification, Kinesis for R-T streaming and processing of large data sets