1 回答
- 最新
- 投票最多
- 评论最多
1
Hi,
There is nothing wrong with Amazon MQ maintenance window. It updates your service with latest versions & install security patches if any available.
You need to implement pattern Amazon MQ active/standby broker for high availability
Maintenance window will first try to install the patches/updates on standby broker. After that it installs on Active broker. During this phase, standby broker will handle the traffic without any downtime.
已回答 2 年前
It's staging environment - I don't need HA in this case. I understand that instance will be unavailable during maintenance window or during reboot. I'm completely ok with that.
I do not understand why lambda trigger does not go back automatically to work after RabbitMQ downtime. It's needed to reenable it.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
As Uchiha_Madara mentioned, Every Amazon MQ broker has a weekly 2-hour maintenance window during which changes are applied. These changes can include broker version updates, configuration changes, or patching of the operating system and other system software. You can minimize downtime during maintenance by using Multi-AZ brokers. (i.e active/standby deployments for high availability)