The document summarizes messaging services on AWS. It provides overviews and details of Amazon MQ, Amazon SQS, Amazon Kinesis, Amazon SNS, Amazon PinPoint, and AWS IoT Message Broker. These services enable event-driven architectures and the exchange of information between distributed systems and microservices through queuing, streaming, and publishing of messages. Key features highlighted include scalability, reliability, encryption, and integration with other AWS services.

1. BADIR - Riyadh
29-12-2018
AWS Messaging
AWS Riyadh
User Group
Ahmed Aziz
21
@Ahmed_Aziz
/in/ahmedsleem
Ahmed.aziz.sleem@gmail.com

2. Agenda
• Events-Driven Architecture
• Overview
• Amazon MQ
• Amazon SQS
• Amazon Kinesis data stream
• Amazon SNS
• Amazon PinPoint
• AWS IoT Message Broker

3. If your application is
cloud-native, or large-scale,
or distributed, and doesn’t
include a messaging component,
that’s probably a bug
Tim Bray
Senior Principe Engineer

4. Events-Driven Architecture

5. Overview
• Enables different systems to communicate or
exchange information.
• Decouple and scale microservices, distributed
systems, and serverless applications.
• Stores messages redundantly across multiple AZs.
• Fully manage service:
– The underlying infrastructure is automatically provisioned
for high availability and message durability to support the
reliability of your applications.

6. Amazon MQ (1 of 2)
• Reduces your operational load by managing the provisioning,
setup, and maintenance of ActiveMQ.
• Uses standards(JMS, NMS, AMQP, STOMP, MQTT, WebSocket)
• There’s no need to rewrite any messaging code when you
migrate to AWS.
• With active/standby brokers, Amazon MQ automatically fails
over to a standby instance.
• Single-instance brokers (if the node fails, it will be unavailable
until it is restarted).

7. Amazon MQ (2 of 2)
• Uses the “network of brokers”.
• Brokers in the network share information about the
clients and destinations each broker hosts.
• You are charged for broker instance and storage usage,
and standard data transfer fees.
• Provides encryption of your messages at rest and in
transit.
• Integrated with AWS Identity and Access Management
(IAM)

8. Amazon SQS (1 of 3)
Standard Queues FIFO Queues
Unlimited Throughput • Up to 300 messages per second.
• Batch: 10 messages per operation(max)
At-Least-Once Delivery Exactly-Once Processing
Best-Effort Ordering First-In-First-Out Delivery
Tag the messages to form an ordered
groups

9. Amazon SQS

10. Amazon SQS (2 of 3)
• Message payload (single/Batch) size is (256 KB)
• Messages more than 256KB  use JAVA extended lib.
• Retain messages in queues up to 14 days (default 4d).
• Long polling is more cost effective than short polling.
• Message is locked once handled by the consumer.
• Message is not getting processed -> lock expired.
• Dead Letter Queue must be the same as source queue.

11. Amazon SQS (3 of 3)
• Exchange sensitive data between applications using
Server-Side Encryption (SSE) to encrypt each message
body.
• AWS Key Management Service (KMS) allows you to
centrally manage the keys that protect SQS messages.
• Transfer data between Amazon SQS and Amazon EC2
or AWS Lambda free of charge within a single region.

12. Amazon Kinesis (1 of 3)
• Collect, process, streaming data and analyze real-time.
• Transform the data before emitting to a data store.
• Designed to scale without limits via increasing the
number of shards.
• Records of a stream are accessible for up to 24 hours,
You can raise this limit to up to 7 days.
• The maximum size of a data blob 1 MB.
• Each shard can support up to 1000PUT records/second.
• It provides ordering of records.

13. Amazon Kinesis (2 of 3)

14. Amazon Kinesis (3 of 3)
Producer 1 Producer 2
Increase throughput Consumer Affinity

15. Amazon SNS (1 of 3)
• Push-based, many-to-many messaging. Using Amazon
SNS topics.
• Pub/Sub messaging architecture.
• Can fan out messages to a large number of endpoints.
• Subscribing endpoints receive only the messages of
interest.
• Data is encrypted in transit, and can also encrypt data
at rest.

16. Amazon SNS (2 of 3)

17. Amazon SNS (3 of 3)
• Push-based, many-to-many messaging uing SNS topics.
• Pub/Sub messaging architecture.
• Can fan out messages to a large number of endpoints.
• Subscribing endpoints filtration.
• Data is encrypted in transit, and at rest.
• maximum limit of 256 KB for published messages. Each
64KB chunk of published data is billed as 1 request.
• First 1 million  free, 1 million  $0.50 thereafter

18. Amazon PinPoint
• Messaging for real-time user engagement.
• Event-based campaigns to your customers when they
take specific actions within your applications.
• Deliverability Dashboard helps you improve your inbox
placement rate.
• Automatic responses when customers send you
messages that contain certain keywords.
• Reach your customers using dedicated, local number

19. AWS IoT Message Broker
• Pub/Sub broker service.
• Sending / receiving of messages to / from AWS IoT.
• Client sends a message addressed to a topic like
Sensor/temp/room1
• The message broker, in turn, sends the message to all
clients that have registered to receive messages for
that topic.
• The topic namespace is isolated for each AWS account
and region pair.

20. Questions

21. See You Next Meetup
AWS Riyadh User Group