Amazon MQ
Developer Guide

Amazon MQ Release Notes

The following table lists Amazon MQ feature releases and improvements. For changes to the Amazon MQ Developer Guide, see Amazon MQ Document History.

Date Documentation Update
June 19, 2019 Amazon MQ is available in the EU (Paris) and Asia Pacific (Mumbai) regions. For information on available regions, see AWS Regions and Endpoints.
June 12, 2019 Amazon MQ is available in the Canada (Central) region. For information on available regions, see AWS Regions and Endpoints.
June 3, 2019

Two new Amazon CloudWatch metrics are available: EstablishedConnectionsCount and InactiveDurableSubscribers. See:

May 10, 2019

Data storage for new mq.t2.micro instance types are limited to 20 GB. See:

April 29, 2019

You can now use tag-based policies and resource-level permissions. For more information, see:

April 16, 2019

You can now retrieve information about broker engine and broker instance options using the REST API. For more information, see:

April 8, 2019

Amazon MQ supports ActiveMQ 5.15.9. For more information, see the following.

Resolved bugs and improvements in ActiveMQ:

For more information:

March 4, 2019 Improved the documentation for configuring dynamic failover and the rebalancing of clients for a network of brokers. Enable dynamic failover by configuring transportConnectors along with networkConnectors configuration options. For more information, see:
February 27, 2019 Amazon MQ is available in the EU (London) Region in addition to the following regions:
  • Asia Pacific (Singapore)

  • US East (Ohio)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Seoul)

  • Asia Pacific (Sydney)

  • EU (Frankfurt)

  • EU (Ireland)

January 24, 2019

The default configuration now includes a policy to purge inactive destinations.

January 17, 2019

Amazon MQ mq.t2.micro instance types now support only 100 connections per wire-level protocol. See, Limits in Amazon MQ.

December 19, 2018 You can configure a series of Amazon MQ brokers in a network of brokers. For more information, see the following sections:
December 11, 2018 Amazon MQ supports ActiveMQ 5.15.8, 5.15.6, and 5.15.0. For more information, see the following:
December 5, 2018 AWS supports resource tagging to help track your cost allocation. You can tag resources when creating them, or by viewing the details of that resource. See Tagging resources.
November 19, 2018 AWS has expanded its SOC compliance program to include Amazon MQ as an SOC compliant service.
October 15, 2018
October 2, 2018 AWS has expanded its HIPAA compliance program to include Amazon MQ as a HIPAA Eligible Service.
September 27, 2018 Amazon MQ supports ActiveMQ 5.15.6, in addition to 5.15.0. For more information, see the following:
August 31, 2018
  • The following metrics are available:

    • CurrentConnectionsCount

    • TotalConsumerCount

    • TotalProducerCount

    For more information, see the Broker Metrics section.

  • The IP address of the broker is displayed on the Details page.

    Note

    For brokers with public accessibility disabled, the internal IP address is displayed.

August 30, 2018 Amazon MQ is available in the Asia Pacific (Singapore) Region in addition to the following regions:
  • US East (Ohio)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Seoul)

  • Asia Pacific (Sydney)

  • EU (Frankfurt)

  • EU (Ireland)

July 30, 2018 You can configure Amazon MQ to publish general and audit logs to Amazon CloudWatch Logs. For more information, see Configuring Amazon MQ to Publish Logs to Amazon CloudWatch Logs.
July 25, 2018 Amazon MQ is available in the Asia Pacific (Tokyo) and Asia Pacific (Seoul) Regions in addition to the following regions:
  • US East (Ohio)

  • US East (N. Virginia)

  • US West (N. California)

  • US West (Oregon)

  • Asia Pacific (Sydney)

  • EU (Frankfurt)

  • EU (Ireland)

July 19, 2018 You can use AWS CloudTrail to log Amazon MQ API calls. For more information, see Logging Amazon MQ API Calls Using CloudTrail.
June 29, 2018 In addition to mq.t2.micro and mq.m4.large, the following broker instance types are available for regular development, testing, and production workloads that require high throughput:
  • mq.m5.large

  • mq.m5.xlarge

  • mq.m5.2xlarge

  • mq.m5.4xlarge

For more information, see Broker Instance Types.

June 27, 2018 Amazon MQ is available in the US West (N. California) Region in addition to the following regions:
  • US East (Ohio)

  • US East (N. Virginia)

  • US West (Oregon)

  • Asia Pacific (Sydney)

  • EU (Frankfurt)

  • EU (Ireland)

June 14, 2018
  • You can use the AWS::Amazon MQ::Broker AWS CloudFormation resource to perform the following actions:

    • Create a broker.

    • Add configuration changes or modify users for the specified broker.

    • Return information about the specified broker.

    • Delete the specified broker.

    Note

    When you change any property of the Amazon MQ Broker ConfigurationId or Amazon MQ Broker User property type, the broker is rebooted immediately.

  • You can use the AWS::Amazon MQ::Configuration AWS CloudFormation resource to perform the following actions:

    • Create a configuration.

    • Update the specified configuration.

    • Return information about the specified configuration.

    Note

    You can use AWS CloudFormation to modify—but not delete—an Amazon MQ configuration.

June 7, 2018 The Amazon MQ console supports German, Brazilian Portuguese, Spanish, Italian, and Traditional Chinese.
May 17, 2018 The limit of number of users per broker is 250. For more information, see Limits Related to Users.
March 13, 2018 Creating a broker takes about 15 minutes. For more information, see Finish creating the broker.
March 1, 2018
January 10, 2018

The following changes affect the Amazon MQ console:

  • In the broker list, the Creation column is hidden by default. To customize the page size and columns, choose .

  • On the MyBroker page, in the Connections section, choosing the name of your security group or opens the EC2 console (instead of the VPC console). The EC2 console allows more intuitive configuration of inbound and outbound rules. For more information, see the updated Enable Inbound Connections section.

January 9, 2018
  • The permission for REST operation ID UpdateBroker is listed correctly as mq:UpdateBroker on the IAM console.

  • The erroneous mq:DescribeEngine permission is removed from the IAM console.

November 28, 2017 This is the initial release of Amazon MQ and the Amazon MQ Developer Guide.
  • Amazon MQ is avaialble in the following regions:

    • US East (Ohio)

    • US East (N. Virginia)

    • US West (Oregon)

    • Asia Pacific (Sydney)

    • EU (Frankfurt)

    • EU (Ireland)

    Using the mq.t2.micro instance type is subject to CPU credits and baseline performance—with the ability to burst above the baseline level (for more information, see the CpuCreditBalance metric). If your application requires fixed performance, consider using an mq.m5.large instance type.

  • You can create mq.m4.large and mq.t2.micro brokers.

    Using the mq.t2.micro instance type is subject to CPU credits and baseline performance—with the ability to burst above the baseline level (for more information, see the CpuCreditBalance metric). If your application requires fixed performance, consider using an mq.m5.large instance type.

  • You can use the ActiveMQ 5.15.0 broker engine.

  • You can also create and manage brokers programmatically using Amazon MQ REST API and AWS SDKs.

  • You can access your brokers by using any programming language that ActiveMQ supports and by enabling TLS explicitly for the following protocols:

  • You can connect to ActiveMQ brokers using various ActiveMQ clients. We recommend using the ActiveMQ Client. For more information, see Connecting a Java Application to Your Broker.

  • Your broker can send and receive messages of any size.