Introduction

This action leverages the AWS Amazon MQ API to trigger a broker reboot.

For ACTIVE_STANDBY and CLUSTER_MULTI_AZ deployments, AWS reboots the requested instance and traffic fails over to the standby/peers.

Use Cases

• Validate that ActiveMQ / RabbitMQ clients reconnect cleanly after a broker reboot.
• Measure recovery time and message-delivery impact during a managed broker restart.
• Exercise the failover path on ACTIVE_STANDBY brokers.

Rollback

This attack does not support rollback.

The reboot is asynchronous on AWS's side and cannot be cancelled once triggered.

Parameters

No parameters.