AWS amazon-mq documentation change
Summary
Updated RabbitMQ version documentation: removed specific version end-of-support dates, restructured content around RabbitMQ 4 and 3 support, added instance type requirements, and simplified upgrade information.
Security assessment
The changes focus on version support details, instance requirements, and documentation restructuring. No security vulnerabilities, patches, or security-specific features are mentioned. Updates recommend RabbitMQ 4.2 but don't cite security reasons.
Diff
diff --git a/amazon-mq/latest/developer-guide/rabbitmq-version-management.md b/amazon-mq/latest/developer-guide/rabbitmq-version-management.md index 464ef148a..268bb8c04 100644 --- a//amazon-mq/latest/developer-guide/rabbitmq-version-management.md +++ b//amazon-mq/latest/developer-guide/rabbitmq-version-management.md @@ -5 +5 @@ -Supported engine versions on Amazon MQ for RabbitMQEngine version upgradesListing supported engine versions +Listing supported engine versions @@ -9 +9 @@ Supported engine versions on Amazon MQ for RabbitMQEngine version upgradesListin -RabbitMQ organizes version numbers according to semantic versioning specification as `X.Y.Z`. In Amazon MQ for RabbitMQ implementations, `X` denotes the major version, `Y` represents the minor version, and `Z` denotes the patch version number. Amazon MQ considers a version change to be major if the major version numbers change. For example, upgrading from version **3**.13 to **4**.0 is considered a _major version upgrade_. A version change is considered minor if only the minor or patch version number changes. For example, upgrading from version 3.**11**.28 to 3.**12**.13 is considered a _minor version upgrade_. +RabbitMQ organizes version numbers according to semantic versioning specification as `X.Y.Z`. In Amazon MQ for RabbitMQ implementations, `X` denotes the major version, `Y` represents the minor version, and `Z` denotes the patch version number. Amazon MQ considers a version change to be major if the major version numbers change. For example, upgrading from version **3**.13 to **4**.0 is considered a major version upgrade. A version change is considered minor if only the minor or patch version number changes. For example, upgrading from version 3.**11**.28 to 3.**12**.13 is considered a minor version upgrade. @@ -11 +11,3 @@ RabbitMQ organizes version numbers according to semantic versioning specificatio -Amazon MQ for RabbitMQ recommends all brokers use the latest supported minor version. For instructions on how to upgrade your broker engine version, see [Upgrading an Amazon MQ broker engine version](./upgrading-brokers.html). +Amazon MQ for RabbitMQ recommends all brokers use the latest supported version RabbitMQ 4.2. For instructions on how to upgrade your broker engine version, see [Upgrading an Amazon MQ broker engine version](./upgrading-brokers.html). + +When you create a new Amazon MQ for RabbitMQ broker, you only need to specify the major and minor version numbers. For example, RabbitMQ 4.2. If you do not specify the engine version when creating a broker, Amazon MQ automatically defaults to the latest engine version. @@ -17,5 +19 @@ Amazon MQ does not support [streams](https://www.rabbitmq.com/streams.html). Cre -Amazon MQ does not support using structured logging in JSON, introduced in RabbitMQ 3.9 - -## Supported engine versions on Amazon MQ for RabbitMQ - -The Amazon MQ version support calendar indicates when a broker engine version will reach end of support. When a version reaches end of support, Amazon MQ upgrades all brokers on this version to the next supported version automatically. This upgrade takes place during your broker's scheduled maintenance windows, within the 45 days following the end-of-support date. +Amazon MQ does not support using structured logging in JSON. @@ -23 +21 @@ The Amazon MQ version support calendar indicates when a broker engine version wi -Amazon MQ provides at least a 90 day notice before a version reaches end of support. We recommend upgrading your broker before the end-of-support date to prevent any disruptions. Additionally, you cannot create new brokers on versions scheduled for end of support within 30 days of the end of support date. +Amazon MQ supports two major version releases of RabbitMQ: @@ -25,7 +23 @@ Amazon MQ provides at least a 90 day notice before a version reaches end of supp -RabbitMQ version | End of support on Amazon MQ ----|--- -3.13 (recommended) | -3.12 | March 17, 2025 -3.11 | February 17, 2025 -3.10 | October 15, 2024 -3.9 | September 16, 2024 + * [RabbitMQ 4](./rabbitmq-4.html) @@ -33 +25 @@ RabbitMQ version | End of support on Amazon MQ -When you create a new Amazon MQ for RabbitMQ broker, you can specify any supported RabbitMQ engine version. If you do not specify the engine version number when creating a broker, Amazon MQ automatically defaults to the latest engine version number. +Amazon MQ supports RabbitMQ 4.2 in the RabbitMQ 4 release series only on the mq.m7g instance type across all supported instance sizes. @@ -35 +27 @@ When you create a new Amazon MQ for RabbitMQ broker, you can specify any support -## Engine version upgrades + * **RabbitMQ 3** @@ -37 +29 @@ When you create a new Amazon MQ for RabbitMQ broker, you can specify any support -You can manually upgrade your broker at any time to the next supported major or minor version. When you turn on [automatic minor version upgrades](https://docs.aws.amazon.com/amazon-mq/latest/api-reference/brokers-broker-id.html#brokers-broker-id-prop-updatebrokerinput-autominorversionupgrade), Amazon MQ will upgrade your broker to the latest supported patch version during the [maintenance window](./maintaining-brokers.html). +Amazon MQ supports RabbitMQ 3.13 in the RabbitMQ 3 release series on mq.t3, mq.m5, and mq.m7g instance types across all supported instance sizes. @@ -39,5 +30,0 @@ You can manually upgrade your broker at any time to the next supported major or -For more information about manually upgrading your broker, see [Upgrading an Amazon MQ broker engine version](./upgrading-brokers.html). - -For all brokers using engine version 3.13 and above, Amazon MQ manages upgrades to the latest supported patch version during the maintenance window. - -###### Important @@ -45 +31,0 @@ For all brokers using engine version 3.13 and above, Amazon MQ manages upgrades -RabbitMQ only allows incremental version updates (ex: 3.9.x to 3.10.x). You cannot skip minor versions when updating (ex: 3.8.x to 3.11.x). @@ -47 +32,0 @@ RabbitMQ only allows incremental version updates (ex: 3.9.x to 3.10.x). You cann -Single instance brokers will be offline while being rebooted. For cluster brokers, the mirrored queues must be synced during reboot. With longer queues, the queue-sync process can take longer. During the queue-sync process, the queue is unavailable to consumers and producer. When the queue-sync process is complete, the broker becomes available again. To minimize the impact, we recommend upgrading during a low traffic time. For more information on best practices for version upgrades, see [Amazon MQ for RabbitMQ best practices](./best-practices-rabbitmq.html). @@ -69 +54 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using LDAP authentication and authorization +Amazon MQ for RabbitMQ @@ -71 +56 @@ Using LDAP authentication and authorization -Security +RabbitMQ 4