Amazon MQ for RabbitMQ: Instance type has reached end of support - Amazon MQ
Resolving RABBITMQ_INSTANCE_TYPE_END_OF_SUPPORT
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Amazon MQ for RabbitMQ: Instance type has reached end of support

Amazon MQ for RabbitMQ raises a RABBITMQ_INSTANCE_TYPE_END_OF_SUPPORT action required code when your broker is running on an instance type that has reached end of support. Support for mq.t3.micro ended on October 1, 2026.

While a broker is in this state, you must migrate it to a supported instance type. A broker that remains on an unsupported instance type becomes unreachable, and your client applications can no longer connect to it. The broker is not deleted, and your broker configuration and message data are retained. You are not billed for the broker while it is unreachable.

Resolving RABBITMQ_INSTANCE_TYPE_END_OF_SUPPORT

  1. Change your broker to a supported instance type using the UpdateBroker API operation, the AWS CLI, or the Amazon MQ console. For the instance types Amazon MQ supports, see RabbitMQ broker instance types.

  2. If your broker is already unreachable and you need more time before changing your instance type, create a case with Support. We can restore connectivity to your broker temporarily so that you can complete the change.

After your broker moves to a supported instance type, Amazon MQ clears the CRITICAL_ACTION_REQUIRED state and your clients can connect again.