EOL.WikiEOL.Wiki
← ← Back to all products

Amazon MQ for ActiveMQ

Active
OtherLatest Version: 5.19Latest Release: N/A

Support summary

Amazon MQ for ActiveMQ 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

5

Latest Version

5.19

Active Support

2

EOL

3

Lifecycle Timeline

Today
5.19
5.19
5.18
5.18
5.17
5.17
5.16
5.16
5.15
5.15
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.19Mar 7, 2025YesNo5.19No
Active
5.18Mar 18, 2023YesNo5.18No
Active
5.17Mar 9, 2022NoJun 16, 20255.17No
EOL
5.16Jun 25, 2020NoNov 15, 20245.16No
EOL
5.15Jun 27, 2017NoSep 16, 20245.15No
EOL

Data sources

Frequently Asked Questions

Which versions of Amazon MQ for ActiveMQ have reached end of life?
The following Amazon MQ for ActiveMQ versions have reached end of life and no longer receive security updates: 5.17, 5.16, 5.15. It is recommended to upgrade to a supported version.
Is it safe to continue using Amazon MQ for ActiveMQ 5.17?
Amazon MQ for ActiveMQ 5.17 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 ActiveMQ?
The latest version of Amazon MQ for ActiveMQ is 5.19, released in the 5.19 release cycle.
How many versions of Amazon MQ for ActiveMQ are currently supported?
Amazon MQ for ActiveMQ currently has 2 actively supported version(s): 5.19, 5.18.
When does Amazon MQ for ActiveMQ 5.19 reach end of life?
Amazon MQ for ActiveMQ 5.19 does not have a specific end-of-life date announced yet.
What should I do when Amazon MQ for ActiveMQ reaches end of life?
When a Amazon MQ for ActiveMQ 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.