Amazon MQ

Managed Apache ActiveMQ or RabbitMQ message broker with standard wire protocols and optional multi-AZ deployment.

Provider: aws
Kind: Queue
Category: Messaging
Official docs: https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/welcome.html

Properties · 5 set by this component

property	type	values	required	kind default	this component
backoff	enum	none \| fixed \| exponential \| exponential-jitter	no	—	inherited
deadLetterQueue	boolean	—	no	false	inherited
delivery	enum	at-most-once \| at-least-once \| exactly-once	yes	—	▸ at-least-once
deploymentMode · component property	enum	single-instance \| active-standby-multi-az \| cluster-multi-az	no	—	inherited
encryptionAtRest · component property	boolean	—	no	true	inherited
engine · component property	enum	activemq \| rabbitmq	no	activemq	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
maxAttempts	integer	—	no	—	inherited
ordering	enum	none \| per-key \| global	no	none	inherited
persistence	boolean	—	no	true	▸ true
replay	boolean	—	no	false	▸ false
retentionDays	integer	—	no	—	inherited
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	▸ work
storageType · component property	enum	efs \| ebs	no	—	inherited
tlsRequired · component property	boolean	—	no	true	inherited

Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Queue without dead-letter queueerror

queue-missing-dlq

A queue that receives asynchronous traffic and has no dead-letter queue either drops poison messages or retries them forever. Neither outcome leaves anything for a human to investigate.

— all of these hold:
— the node's `deadLetterQueue` is false
— the node has at least one asynchronous incoming edge

Retry queue without dead-letter queueerror

retry-queue-without-dlq

A retry queue is where poison messages end up. With no dead-letter queue they are retried forever or dropped in silence, and nobody ever looks at the failed payment.

— all of these hold:
— the node's `role` is "retry"
— the node's `deadLetterQueue` is false

Retry queue without backoffwarning

retry-without-backoff

Retrying a transient failure at full speed turns one slow dependency into a retry storm. A retry queue backs off, preferably exponentially and with jitter.

— all of these hold:
— the node's `role` is "retry"
— any of these hold:
— the node's `backoff` has no value
— the node's `backoff` is "none"

Use it in a design

nodes:
  - { id: "mq", component: "aws-mq" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Amazon MQ: managed Apache ActiveMQ Classic or RabbitMQ broker; AWS runs maintenance and version
3# upgrades in a scheduled window. "Data protection in Amazon MQ" says data is always encrypted at
4# rest (Amazon MQ owned KMS key by default) and TLS is required for all client connections;
5# "Deployment options" shows a broker is one instance in one AZ unless you pick active/standby.
6schemaVersion: "1"
7type: "component"
8id: "aws-mq"
9kind: "queue"
10provider: "aws"
11docs: "https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/welcome.html"
12defaults:
13  managed: true
14  delivery: "at-least-once"
15  persistence: true
16  replay: false
17  role: "work"
18properties:
19  engine:
20    type: "enum"
21    values: ["activemq", "rabbitmq"]
22    default: "activemq"
23  deploymentMode:
24    type: "enum"
25    values: ["single-instance", "active-standby-multi-az", "cluster-multi-az"]
26  storageType:
27    type: "enum"
28    values: ["efs", "ebs"]
29  encryptionAtRest:
30    type: "boolean"
31    default: true
32  tlsRequired:
33    type: "boolean"
34    default: true

The same page as markdown, for an agent: /catalogue/components/aws-mq.md