- Newest
- Most votes
- Most comments
I apologize, but there seems to be a misunderstanding in your statement. Let me clarify the situation regarding automatic minor version upgrades for Amazon MQ with RabbitMQ:
For RabbitMQ engine version 3.13 and above on Amazon MQ, AWS manages upgrades to the latest patch version automatically. However, this does not mean that the "automatic minor version upgrade" setting is always enabled or that you can't interact with it.
The "automatic minor version upgrade" setting still exists and can be controlled. This setting determines whether your broker will automatically upgrade to new minor versions (e.g., from 3.13.x to a future 3.14.x) when they become available.
You can enable or disable this setting using the AWS Management Console, AWS CLI, or Amazon MQ API. If you're having trouble modifying this setting in the console, you might want to try using the AWS CLI or API instead.
For example, using the Amazon MQ API, you can update the broker settings with the UpdateBroker operation. You would set the "autoMinorVersionUpgrade" property to "true" in the request payload.
If you're using Terraform and encountering issues, you might need to ensure that your Terraform AWS provider is up to date, as older versions might not correctly handle this setting for newer RabbitMQ versions.
Remember, enabling automatic minor version upgrades is generally recommended as it ensures your broker receives the latest security patches and bug fixes. If you're still encountering issues after trying these approaches, it would be advisable to contact AWS support for further assistance.
Sources
Managing Amazon MQ for RabbitMQ engine versions - Amazon MQ
Upgrading an Amazon MQ broker engine version - Amazon MQ
For anyone else seeing this - I found the solution myself. This setting cannot be changed in the AWS console or in the arguments given to terraform, but it can be changed in the AWS CLI like so:
aws mq update-broker --broker-id <mq broker id here> --auto-minor-version-upgrade