Amazon MQ Supports Throughput-Optimized Brokers Using Amazon Elastic Block Store (EBS)

Amazon MQ supports creating throughput-optimized brokers by using Amazon Elastic Block Store (EBS)—instead of the default Amazon Elastic File System (Amazon EFS)—for broker storage. To take advantage of high durability and replication across multiple Availability Zones, use Amazon EFS. To take advantage of low latency and high throughput, use Amazon EBS.

Important

• You can use Amazon EBS only with the mq.m5 broker instance type family.
• Although you can change the broker instance type, you can't change the broker storage type after you create the broker.
• Amazon EBS replicates data within a single Availability Zone and doesn't support the active/standby deployment mode.

For more information, see the following in the Amazon MQ Developer Guide:

• Broker Storage
• Choose the Correct Broker Storage Type for the Best Throughput
• BurstBalance, VolumeReadOps, and VolumeWriteOps metrics in the Broker Metrics

See also the storageType property of the broker-instance-options resource in the Amazon MQ REST API Reference.

Amazon MQ Limit for Groups per User is Increased

The maximum number of groups per user is 20. The maximum number of connections per broker, per wire-level protocol is 1,000.

Amazon MQ is a HIPAA Eligible Service

AWS has expanded its HIPAA compliance program to include Amazon MQ as a HIPAA Eligible Service.

Amazon MQ Supports ActiveMQ 5.15.6

Amazon MQ supports ActiveMQ 5.15.6, in addition to 5.15.0. For more information, see Broker Engine in the Amazon MQ Developer Guide, Release Notes in the ActiveMQ documentation, and ActiveMQ Client 5.15.6.

Three New Amazon MQ Metrics Are Available

• The CurrentConnectionsCount, TotalConsumerCount, and TotalProducerCount metrics are available. For more information, see Broker Metrics in the Amazon MQ Developer Guide.
• 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.

Amazon MQ is Available in the Asia Pacific (Singapore) Region

Amazon MQ is available in the Asia Pacific (Singapore) Region in addition to the 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), and EU (Ireland) Regions.

Integration with Amazon CloudWatch Logs

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 in the Amazon MQ Developer Guide.

Amazon MQ is Available in the Asia Pacific (Tokyo) and Asia Pacific (Seoul) Regions

Amazon MQ is available in the Asia Pacific (Tokyo) and Asia Pacific (Seoul) Regions in addition to the US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Sydney), EU (Frankfurt), and EU (Ireland) Regions.

Integration with AWS CloudTrail

You can use AWS CloudTrail to log Amazon MQ API calls. For more information, see Logging Amazon MQ API Calls Using CloudTrail in the Amazon MQ Developer Guide.

Amazon MQ is Available in the US West (N. California) Region

Amazon MQ is available in the US West (N. California) Region in addition to the US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), EU (Frankfurt), and EU (Ireland) Regions.