DevOps Community Sponsored by Cloud Posse

SweetOps

Because `mq.t3.micro` is only available for ActiveMQ. For RabbitMQ, the instance types start at `large`, on either the `m5` or `m7g` generations.

```aws mq describe-broker-instance-options --engine-type ACTIVEMQ | jq -r '.BrokerInstanceOptions[] | .HostInstanceType'
mq.m5.2xlarge
mq.m5.2xlarge
mq.m5.4xlarge
mq.m5.4xlarge
mq.m5.large
mq.m5.large
mq.m5.xlarge
mq.m5.xlarge
mq.t3.micro```
```aws mq describe-broker-instance-options --engine-type RABBITMQ | jq -r '.BrokerInstanceOptions[] | .HostInstanceType'
mq.m5.2xlarge
mq.m5.4xlarge
mq.m5.large
mq.m5.xlarge
mq.m7g.12xlarge
mq.m7g.16xlarge
mq.m7g.2xlarge
mq.m7g.4xlarge
mq.m7g.8xlarge
mq.m7g.large
mq.m7g.medium
mq.m7g.xlarge```

Additionally, `micro` should only be selected for a demo or testing purposes. While lower cost, it shouldn't run production applications or be in the path of application teams.