🛡️ AWS MQ Broker engine version is outside Amazon MQ support🟢

• Contextual name: 🛡️ Broker engine version is outside Amazon MQ support🟢
• ID: /ce/ca/aws/mq/broker-engine-support
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: RELIABILITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 AWS MQ Broker
  • 🔌 AWS MQ Broker - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies AWS MQ Brokers whose current ActiveMQ or RabbitMQ engine minor version has reached its published Amazon MQ end of support (EOS) date.

Rationale

Supported engine versions receive security patches, bug fixes, and other improvements. After EOS, Amazon MQ schedules an automatic upgrade within 45 days. Identifying brokers that remain on an EOS version helps teams resolve overdue upgrades and control application compatibility and maintenance risk.

Impact

Upgrades can interrupt message processing and may require application or configuration changes, especially across RabbitMQ major versions. An automatic upgrade scheduled after EOS does not extend engine support.

Audit

This policy marks an AWS MQ Broker as INCOMPLIANT if its State is RUNNING, REBOOT_IN_PROGRESS, CRITICAL_ACTION_REQUIRED, or REPLICA, and its current Engine Type and Engine Version match one of the following known Amazon MQ end-of-support versions.

| Engine type | Minor version | End of support |

... see more

Remediation

Open File

Remediation

Prepare a supported upgrade

1. Open the broker in the Amazon MQ console in its AWS Region. Review the current engine version, pending changes, deployment mode, instance type, maintenance window, and any action-required codes.

2. Check the Amazon MQ support calendar for the broker's engine. List the available versions for its Region and instance type:

   aws mq describe-broker-instance-options \
     --region REGION \
     --engine-type ENGINE_TYPE \
     --host-instance-type INSTANCE_TYPE

   Replace REGION and INSTANCE_TYPE with the broker's values. Set ENGINE_TYPE to ACTIVEMQ or RABBITMQ.

3. Select an available, supported target version. Test producers, consumers, authentication, and broker configuration against it. For cross-Region replication pairs, coordinate both brokers' upgrades and verify replication health.

4. Follow the engine's supported upgrade sequence and complete its prerequisites.

RabbitMQ upgrade requirements

• Minor upgrades cannot skip intermediate minor versions.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Infrastructure Modernization			39		no data