← ← Back to all products
Amazon MQ for RabbitMQ
Active
OtherLatest Version: 4.2Latest Release: N/A
Support summary
Amazon MQ for RabbitMQ currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
2
0 lts
Versions
3
Latest Version
4.2
Active Support
2
EOL
1
Lifecycle Timeline
Today ↓
4.2
4.2
3.13
3.13
3.12
3.12
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.2 | Oct 27, 2025 | Yes | No | 4.2 | No | Active |
| 3.13 | Feb 22, 2024 | Yes | No | 3.13 | No | Active |
| 3.12 | Jun 1, 2023 | No | Mar 17, 2025 | 3.12 | No | EOL |
Data sources
Frequently Asked Questions
Which versions of Amazon MQ for RabbitMQ have reached end of life?
The following Amazon MQ for RabbitMQ versions have reached end of life and no longer receive security updates: 3.12. It is recommended to upgrade to a supported version.
Is it safe to continue using Amazon MQ for RabbitMQ 3.12?
Amazon MQ for RabbitMQ 3.12 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Amazon MQ for RabbitMQ?
The latest version of Amazon MQ for RabbitMQ is 4.2, released in the 4.2 release cycle.
How many versions of Amazon MQ for RabbitMQ are currently supported?
Amazon MQ for RabbitMQ currently has 2 actively supported version(s): 4.2, 3.13.
When does Amazon MQ for RabbitMQ 4.2 reach end of life?
Amazon MQ for RabbitMQ 4.2 does not have a specific end-of-life date announced yet.
What should I do when Amazon MQ for RabbitMQ reaches end of life?
When a Amazon MQ for RabbitMQ version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.