Ensure Amazon MQ broker instances are using desired instance types

Security & Compliance

To ensure that the Amazon MQ broker instances provisioned in your AWS account are configured with the appropriate instance type for your Apache ActiveMQ workload, it is recommended to verify the instance type settings. An MQ broker instance refers to a broker environment running in the AWS cloud. By setting limits on the type of Amazon MQ broker instances that can be created in your AWS account, you can ensure compliance with internal requirements and avoid unexpected charges on your AWS bill.


Here are some remediation steps you can take to ensure that your Amazon MQ broker instances are using the desired instance types:

  1. Log in to the AWS Management Console and navigate to the Amazon MQ console.
  2. Select the Amazon MQ broker instance for which you want to verify the instance type.
  3. Click on the "Configuration" tab and scroll down to the "Broker instance" section.
  4. Check the current instance type and compare it to the desired instance type for your workload.
  5. If the current instance type does not match the desired instance type, stop the broker instance.
  6. Modify the broker instance to use the desired instance type by selecting the instance type from the drop-down list.
  7. Start the broker instance and verify that it is using the desired instance type.
  8. Repeat these steps for each Amazon MQ broker instance to ensure that they are using the desired instance types.

By following these remediation steps, you can ensure that your Amazon MQ broker instances are configured with the appropriate instance types for your workload. This will help you to optimize performance and cost-effectiveness, while also ensuring compliance with internal requirements.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.