View a markdown version of this page

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 Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

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.

Migrate your broker to a supported instance type to keep your client applications connected. You can change your broker's instance type yourself at any time, including after the broker has become unreachable.

The broker isn't deleted. Amazon MQ retains your broker configuration and message data, and doesn't bill you for the broker while it's unreachable.

Important

A broker that remains on an unsupported instance type becomes unreachable. Your client applications can no longer connect to it.

Resolving RABBITMQ_INSTANCE_TYPE_END_OF_SUPPORT

The following procedure changes your broker to a supported instance type. Use it whether your broker is still reachable or has already become unreachable.

Both steps are required

UpdateBroker records the instance type change but doesn't apply it. If your broker is unreachable, it remains unreachable until you complete step 2.

To change the instance type

  1. Call UpdateBroker with hostInstanceType set to a supported instance type, or change the instance type in the Amazon MQ console. For more information about supported instance types, see RabbitMQ broker instance types. For console and Amazon CLI procedures, see Upgrading an Amazon MQ broker instance type.

  2. Call RebootBroker, or choose Actions, Reboot broker in the Amazon MQ console.

  3. Call DescribeBroker until brokerState is RUNNING and actionsRequired no longer contains RABBITMQ_INSTANCE_TYPE_END_OF_SUPPORT.

What to expect

Expect the following during the change:

  • The broker reports CRITICAL_ACTION_REQUIRED until the change completes, then returns to RUNNING.

  • The change takes several minutes. The broker is unavailable until it completes.

  • Amazon MQ retains your broker configuration and message data.

  • You can't change the broker back to mq.t3.micro.

Important

Billing resumes when your broker returns to service, at the rate for the new instance type.

Handling an incomplete change

If your broker doesn't return to RUNNING, create a case with Amazon Web Services Support. Also create a case if DescribeBroker still reports RABBITMQ_INSTANCE_TYPE_END_OF_SUPPORT after the reboot completes.

If you need more time before changing your instance type, create a case with Amazon Web Services Support. Amazon Web Services Support can restore connectivity to your broker temporarily so that you can retrieve your messages or 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.