Questions tagged with Amazon MQ

AWS Lambda function triggered by Amazon MQ: RabbitMQ event source. It works fine and consumes messages from the queue, but It does not scale with respect to the queue load. - Lambda function uses Unreserved account concurrency and it is 1000 but concurrency is usually around 2 or 1. - Batch_Size and Batch_window parameters do not affect the consumption speed much. Is there any configuration need to be considered to make the lambda function adapt its queue consumption speed to queue load?

Hi, I would like to install "rabbitmq_delayed_message_exchange" plugin to my AmazonMQ, how could I do that? Thanks.

Hi there, I have an amazonMQ with the broker connection limit of 100. Normally, I use open connection and it only use 37 connection. But in the meantime, I see there are an increment in the connection, I though that because my pods are down, so the system connect with the new pods. Unfortunately, the dead connection is still there although the doc for amazonmq, there is a note: Check your client-side logs for further details. The broker will clean up inactive TCP connections after 600000 ms, and free up the connection socket. Here is the screenshot of Cloudwatch for my ActiveMQ connection https://i.ibb.co/MMzg8sB/Image-from-i-OS.jpg Here is my policy entry configuration: ``` <policyEntry gcInactiveDestinations="true" inactiveTimoutBeforeGC="60000" topic="&gt;"> <!-- The constantPendingMessageLimitStrategy is used to prevent slow topic consumers to block producers and affect other consumers by limiting the number of messages that are retained For more information, see: http://activemq.apache.org/slow-consumer-handling.html --> <pendingMessageLimitStrategy> <constantPendingMessageLimitStrategy limit="1000"/> </pendingMessageLimitStrategy> </policyEntry> ```

Hello, I am coding now AWS lambda function, and I connected it to RabbitMQ broker. I created a queue on RabbitMQ and I connected this queue to topic by Routing Key. When I send message to RabbitMQ topic, it sends message to the queue and it is triggered to the AWS Lambda function and now I need 'routing key' in the lambda function. How can I get this routing key? Regards, Can

We are using Amazon MQ (Apache MQ), along with STOMP to deliver content to our customers. We wish to keep the connection alive using heartbeats and on the client are setting incoming to 10s and outgoing to 10s, however we occasionally see heartbeat timeouts, I believe due to servers strict enforcement of timeouts. For our local Apach MQ test server we can avoid this problem by setting "hbGracePeriodMultiplier=1.5" like so: ``` <transportConnectors> <transportConnector name="stomp" uri="stomp://localhost:61613?transport.hbGracePeriodMultiplier=1.5"/> </transportConnectors> ``` See Active MQ documentation for Heatbeats: https://activemq.apache.org/stomp However on AWS MQ configuration for transportConnector (https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/permitted-attributes.html#transportConnector.attributes), there is no uri or relevant attribute listed. Am I missing something - is anyone aware of a way to configure a heartbeat grace period on AWS MQ?

As active mq classic will not be supported by upcoming spring boot 3. Any plan to support Artemis in MQ in near future?

Hi, I have an ActimeMQ cluster with the RabbitMQ engine on AWS, that cluster is on a private network in the VPC. I need to generate an event based on the S3 PutObject call and send a message to the RabbitMQ cluster. I thought I could do it with S3-> EventBridge Events-> Rule-> API Endpoint and send the transformed message to the RabbitMQ API (https://ID.mq.eu-west-1.amazonaws.com/api/exchanges/%2f/amq.default/publish). Despite configuring all this and seeing in the API Destinations: Status Active and Connections: Authorized, I see the following message from the events: Unable to invoke ApiDestination endpoint: Timeout calling endpoint for API Destination: socket closed. What I want to do is allowed by EventBridge? i.e. make a call to the RabbitMQ API of a private cluster that is in the same account. Regards!

Hi, I need to subscribe to AMQP broker which is hosted outside of AWS and consume the content. Is there a serverless service that is able to maintain the connection without need to run an EC2 instance and forward the data to other services? I have tried to work with Kinesis and EventBridge, but these services doesn't seem to be able to consume amqp, while MQ is only able to setup a broker.

The default connection string is used with failover without any parameter where randomize parameter by default is “true”, [Apache documentation](https://activemq.apache.org/failover-transport-reference.html.) suggests to set this to false if you want to connect to primary first and connect to secondary only when primary fails I consider to set the “randomize” parameter to “false”, because only one/first broker is active in active/standby case. [AWS doc](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/connecting-to-amazon-mq.html) suggests to set randomize=true for Active/Standby , could you explain why? Shouldn't it be set to false ?

I built an MQTT client in Java using Amazon's provided SDK (software.amazon.awssdk.crt.mqtt.MqttClientConnection, and related classes). I've been testing it by running it on my workstation, and it's been working fine. Today I tried running the same code on an EC2 instance, and got this exception. I can't figure out why. java.util.concurrent.ExecutionException: software.amazon.awssdk.crt.mqtt.MqttException: TLS (SSL) negotiation failed at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928) at cgp.aws.IOTSubscriber.<init>(IOTSubscriber.java:105) at cgp.Thing.main(Thing.java:23) Caused by: software.amazon.awssdk.crt.mqtt.MqttException: TLS (SSL) negotiation failed at software.amazon.awssdk.crt.mqtt.MqttClientConnection.onConnectionComplete(MqttClientConnection.java:139)

In creating an Mqtt client connection using the class AwsIotMqttConnectionBuilder, I encounter a configuration setting called "withCleanSession(boolean)" that is described in the documentation this way: /** * Configures whether or not the service should try to resume prior * subscriptions, if it has any * * @param cleanSession true if the session should drop prior subscriptions when * a connection from this builder is established, false to resume the session * @return {@link AwsIotMqttConnectionBuilder} */ public AwsIotMqttConnectionBuilder withCleanSession(boolean cleanSession) { this.config.setCleanSession(cleanSession); return this; } What is the meaning of "session" in this context? Is a session something that is local to one computer, or is it a state stored on the network somewhere? Is the client ID of the connection related to its state?

Is it possible to send an MQTT message and have it only be delivered once, to one subscriber, even if there are multiple subscribers on the topic? The situation I'm thinking of is when I have a cluster of servers on performing the same function. There is more than one server for purposes of redundancy and load balancing, but when a message is published to a topic, I only want one server to respond. Thanks, Frank

I'm trying to build a Java client that subscribes to IoT services topics. In the IoT console, I went to the MQTT test client and subscribed to a topic named "test". In my Java code, I set up an MqttClientConnection. For the endpoint, I gave the value returned by IotClient.describeEndpoint(). I also gave my AWS credentials. I'm able to instantiate the client, connect, and publish a message to the "test" topic without encountering any exceptions. However, the message doesn't appear in the AWS console. Similarly, I can subscribe to the topic, but messages I publish via the console don't show up in the Java application. I suspect the problem is that the topic name is not simply "test", but some string that has a prefix which associates it with IoT services. I can't find any documentation to this effect, though. Thanks, Frank

Hi, I'm working with IOT services using the Java SDK. I'm able to instantiate an IotClient (software.amazon.awssdk.services.iot.IotClient) and perform some basic functions like listThings() or describeEndpoint(). So I know my integration and credentials are working as expected. The next thing I need to do is work with the message queues (MQTT) associated with my IOT things. I'm a bit confused here. I see that there is a package called mq, which contains an MqClient; I've imported that package into my project and I can create the MqClient (and I've also made sure my credentials have full access to MQ). I'm not sure what to do next. The MqClient doesn't appear to have any functions related to sending or receiving messages. I'm also not sure how to configure it to work with the message queues used by IOT services, as opposed to others. Do I need some kind of third-party MQTT client? I've noticed that some are available and I think MQ is a non-proprietary protocol, but I'd definitely prefer to steer clear of random third-party pacakges if the functionality I need is available from the AWS Java SDK. Thanks, Frank

When connecting to the active broker ActiveMQ via JMS in java without a failure url (e.g. ssl://broker_address), the activeMQ redelivery plugin works as expected, i.e retries X times before moving to the DLQ. When copying the Java failover string from the AWS MQ console ( failover:(ssl://broker1:61617,ssl://broker2:61617), and using that to connect, the re-delivery plugin no longer functions as expected. The scheduler runs, and messages are infact re-dispatched, but the the activeMQ java consumer throws an exception, stating "suppressing duplicate delivery on connection". Note everything else remained constant between testing with a failure url and testing without the failure url. Version of ActiveMQ being used is 5.16.3. The first thing I want to ask, is anyone using redelivery plugin with failover strings successfully? Secondly, anyone have the specific issue I've faced and can suggest any solutions? =====SOLUTION======= This ended up being a problem with the default client library for activemq with springboot, upgrading the activemq library to 5.16.3 fixed this bug.

I'm getting an error when viewing any queue in my AWS MQ ActiveMQ broker: "Exception occurred while processing this request, check the log for more information!" When I check the logs, I see a couple errors [1]. I then found the [troubleshooting step related to this error](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/troubleshooting-activemq.html#issues-jsp-exception). The recommended fix was to give the `activemq-webconsole` group read/write/admin rights on all topics and queues. This made no difference. I also tried making the user I was logging into the console with a member of that group, and that had no effect. Does anyone know what is needed to be able to view queues in the console of an AWS MQ ActiveMQ broker? [1] > WARN | Security Error occurred on connection to: vm://localhost#4, User amazonmq-system-13e98d69-51c6-4474-ae0a-54deefb2b1bc is not authorized to read from: queue://new-space | org.apache.activemq.broker.TransportConnection.Service | ActiveMQ VMTransport: vm://localhost#5-2 > WARN | /admin/browse.jsp | org.eclipse.jetty.server.HttpChannel | qtp672313607-85 javax.servlet.ServletException: javax.servlet.ServletException: org.apache.jasper.JasperException: An exception occurred processing [/browse.jsp] at line [48] 45: </tr> 46: </thead> 47: <tbody> 48: <jms:forEachMessage queueBrowser="${requestContext.queueBrowser.browser}" var="row"> 49: <tr> 50: <td><a href="<c:url value="message.jsp"> 51: <c:param name="id" value="${row.JMSMessageID}" /> Stacktrace: at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.Server.handle(Server.java:500)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at java.lang.Thread.run(Thread.java:750)[:1.8.0_322] 2022-02-25 21:40:14,966 | WARN | /admin/browse.jsp | org.eclipse.jetty.server.HttpChannel | qtp672313607-85 javax.servlet.ServletException: javax.servlet.ServletException: org.apache.jasper.JasperException: An exception occurred processing [/browse.jsp] at line [48] 45: </tr> 46: </thead> 47: <tbody> 48: <jms:forEachMessage queueBrowser="${requestContext.queueBrowser.browser}" var="row"> 49: <tr> 50: <td><a href="<c:url value="message.jsp"> 51: <c:param name="id" value="${row.JMSMessageID}" /> Stacktrace: at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.Server.handle(Server.java:500)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at java.lang.Thread.run(Thread.java:750)[:1.8.0_322]

1. We have setup 2 private rabbitmq broker clusters(rabbitmq-prod & rabbitmq-test) in our VPC on the same subnets. 2. Created security groups that allow traffic from 0.0.0.0/0 to port 5671 and allow all outgoing traffic. 3. Created shovel on rabbitmq-prod that sends traffic to rabbitmq-test. But the shovel stays in "starting" state, and the logs says that the connection times out. Is there any more configuration that has to be done. Or doesn't the implementation support shovels to private brokers?

I have created RabbitMQ instance in AWS, it works and Web Console works too. I have created an exchange, queue bound with it and message. All works. Then I try the c# code , the host and port I have got from AWS RabbitMQ config. `ConnectionFactory connectionFactory = new ConnectionFactory(); connectionFactory.Port = 5671; connectionFactory.HostName = "amqps://prefix.mq.us-east-1.amazonaws.com"; connectionFactory.HostName = "prefix.mq.us-east-1.amazonaws.com"; connectionFactory.UserName = "admin"; connectionFactory.Password = "mypwd"; try { IConnection connection = connectionFactory.CreateConnection(); } catch(Exception x) { Console.WriteLine("TEST: {0}", x.Message); }` The result is: "x.Message = "None of the specified endpoints were reachable"" Where am I wrong? How to fix it?

I am struggeling with an issue which appeared out of a sudden between two deployments of our application. What we are doing is. There is a lambda function which has an EventSource configured. In this case it is a MessageQueue (MQ) Event, listening to a AmazonMQ RabbitMQ Broker. It worked fine for many months but with todays deployment it failed. Last working deployment: 2022-02-02 11:06:16 UTC+0100 Error: ``` Resource handler returned message: "Invalid request provided: Invalid parameters: VIRTUAL_HOST (Service: Lambda, Status Code: 400, Request ID:, Extended Request ID: null)" (RequestToken: , HandlerErrorCode: InvalidRequest) ``` Template excerpt: ``` ConsumerFunction: Type: 'AWS::Serverless::Function' Properties: CodeUri: . Events: MQEvent: Type: MQ Properties: BatchSize: 120 Enabled: true Broker: 'arn:aws:mq:us-east-1:11111:broker:cwv-broker:11111' Queues: - 'consumer-queue-name' SourceAccessConfigurations: - Type: BASIC_AUTH URI: 'arn:aws:secretsmanager:us-east-1:1111:secret:global-secrets/rabbitmq-broker-credentials' - Type: VIRTUAL_HOST URI: '/consumervhost' FunctionName: 'consumer-v1-prod' Handler: handler/consumer.php Layers: - !Sub 'arn:aws:lambda:${AWS::Region}:209497400698:layer:php-80:16' - !Sub 'arn:aws:lambda:${AWS::Region}:403367587399:layer:redis-php-80:11' MemorySize: 250 Policies: - AWSSecretsManagerGetSecretValuePolicy: SecretArn: 'arn:aws:secretsmanager:us-east-1:11111:secret:global-secrets/rabbitmq-broker-credentials' - VPCAccessPolicy: {} - !Ref CwvMqAccessPolicy ReservedConcurrentExecutions: 5 Runtime: provided.al2 Timeout: 900 VpcConfig: SecurityGroupIds: - !ImportValue MainVPC-DefaultSecurityGroup SubnetIds: - !ImportValue MainVPC-SubnetPrivateA - !ImportValue MainVPC-SubnetPrivateB Parameters: RetentionDays: 1 ``` Sam version: SAM CLI, version 1.37.0 Deployment script: ``` sam package \ --output-template-file /tmp/deploy-stack.yaml \ --s3-bucket "deployment-resources" \ --profile "$AWS_PROFILE" sam deploy \ --template-file /tmp/deploy-stack.yaml \ --s3-bucket "deployment-resources" \ --capabilities CAPABILITY_IAM \ --stack-name "consumer-prod-v1" \ --profile "$AWS_PROFILE" ``` Help is much appreciated.

I need to use an alternative port for RabbitMQ 5672. Following instructions, I found out I can use a NLB to connect to AmazonMQ RabbitMQ but I found an issue regarding available plugins on AWS RabbitMQ. It doesn't support (yet?) rabbitmq-event-exchange which is a very simple plugin that publish internal events to a topic and allow to subscribe to those. Maybe someone in the service team can provide a hint if this plugin is in the short term map or any workaround for this?

I've got an issue related to lambda triggering from Amazon MQ for RabbitMQ. In my case everything works fine until RabbitMQ will be rebooted (or runs into maintenance window). In trigger details I can see then message: `last processing result: PROBLEM: Failed to connect with event source.` And in Rabbit logs:: ``` closing AMQP connection <0.21044.6> (10.0.25.82:3459 -> 10.0.17.86:5672): missed heartbeats from client, timeout: 30s ``` The only one way to fix this is to reenable trigger in lambda configuration. Issue does not happen on every reboot, it's needed to perform it several times (every 3-4 reboots I think). Does anyone has an idea what's going wrong here?

Hi, I am helping a customer who wants to achieve 320TPS with a NoB of 3 Brokers in a mesh for a message size between 500KB-1MB. Can we achieve this?

I want to use a single Active MQ Queue and have it invoke lambda functions. I want to enforce order but also have parallelism. Active MQ has a concept of "Message Groups" which sounds perfect. Does the AWS lambda support Message Groups and will invoke different instance of lambda synchronously with different message groups as required based on load ?

Hello, Do you know if there is a way to configure the `consumer_timeout` (delivery acknowledgment) parameter of RabbitMQ in AmazonMQ? https://www.rabbitmq.com/consumers.html#acknowledgement-timeout Our instances got automatically upgraded and we now have timeout errors for our tasks with long ETAs. Thank you very much for your help!

Hi, I'm trying to connect the RabbitMQ using php, and getting error. PhpAmqpLib\Exception\AMQPDataReadException: Error receiving data in /Users/surya/projects/rabbitmq/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Wire/IO/StreamIO.php:184 However, I'm able to connect to any other local instance/ docker instance using the same code. I'm following the guidelines present on the RabbitMQ Official Tutorials. https://www.rabbitmq.com/tutorials/tutorial-one-php.html What I can? 1. Telnet to the 5671 and 15671 Port. - Success. 2. Open the Management console using the UI and successful login. Please let me know, incase any other information is required from my side. Thanks, Surya

Hello, I'm trying to connect to a non-public RabbitMQ using nodejs and I keep getting the following error no matter what I've tried... Error: Handshake terminated by server: 403 (ACCESS-REFUSED) with message "ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile. All docs for RabbitMQ + SSL stating the use of certificates. However, and AFAICT, cert authentication is not currently supported on AmazonMQ. So my question is, what exactly is needed in order to successfully connect to a RabbitMQ broker over SSL on AmazonMQ. Example of nodejs with amqplib would be highly appreciated. Thanks! Edited by: karadikid on May 31, 2021 8:02 AM

A very simple connection, the RabbitMQ broker has Public accessibility= Yes On factory.newConnection(),, using Java1.8 & amqp-client-5.12.0.jar (latest), getting the above exception. //factory is set: factory.setUsername(queueUser); factory.setPassword(queuePassword); factory.setVirtualHost("/"); factory.setHost(queueHost); factory.setPort(5671); and the queueHost is set to the AMQP Endpoints on the RabbitMQ console. This should be a 5 minutes setup, but I already spent way too much time on this. I have not set this broker, nor do I see how to set it, with IPv6. I just need simple Ipv4 to work. Any idea ?

Hi, I am creating a cluster deployment of Amazon MQ (with RabbitMQ engine). Are the broker IP addresses static? and is it also true after maintenance? Thank you.

I've seen that the terraform provider is improving but along with the AWS CLI doesn't allow us to specify some of configuration available via. the web console, e.g. VPC. Is this something coming up or a known gap that will be maintained?

Hello, I was wondering if the RabbitMQ Prometheus metrics are available (https://www.rabbitmq.com/prometheus.html)? The default port 15692 does not seem to be exposed. This would allow us to integrate these metrics into our existing alerting system. Thanks Jonas

How does one configure ActiveMQ to use MQTT over Websockets ? I was unable to find proper documentation on how to set up the configuration file for this. However, I tried adding the following lines to the configuration file **<transportConnectors>** **<transportConnector name="mqtt+wss" uri="wss://myURLhere:61620"/>** **</transportConnectors>** This produced the following error The specified XML configuration data is invalid: cvc-attribute.3: The value 'mqtt_ws' of attribute 'name' on element 'transportConnector' is not valid with respect to its type, 'protocol'. and cvc-enumeration-valid: Value 'mqtt_ws' is not facet-valid with respect to enumeration '\[ openwire ]'. It must be a value from the enumeration. Any help to resolve the issue would be appreciated. Thanks ! Edited by: abhai on Feb 23, 2021 10:47 PM Edited by: abhai on Feb 23, 2021 10:47 PM Edited by: abhai on Feb 23, 2021 10:48 PM

I set up an Amazon MQ instance in a VPC and configured an MQ trigger to invoke a Lambda function. The function is assigned to the same VPC and Security Group as the Amazon MQ instance, but the MQ trigger keeps returning the following error: **PROBLEM: Connection error. Please check your event source connection configuration.** If I make the Amazon MQ instance publicly accessible, the MQ trigger invokes the function. However, I can't make the Amazon MQ instance publicly accessible because of security requirements. Is there a way to have the MQ trigger invoke the Lambda function without making the Amazon MQ instance public?

Hi everyone, I just created a broker (RabbitMQ) and here are my details: - Broker status: Running - Broker engine: RabbitMQ - Deployment mode: Single-instance broker - Broker engine version: 3.8.6 - Public accessibility: No Additionally, my Security group settings (Inbound rules) are the following: - All traffic, All, All, 0.0.0.0/0 (I'll set IP later) However, when I click on the link - it doesn't work. It works when I create a new broker with Public accessibility as Yes. Anyway, I don't want that. I'd prefer setting as 'No' with SG settings. Does anyone know what could be wrong here? I'd like to have web app access too. p.s. in VPC I have: - DNS hostnames: Enabled - DNS resolution: Enabled Thanks! Edited by: Nedim on Dec 15, 2020 3:39 PM

Hello, thanks for supporting RabbitMQ as an engine of Amazon MQ. As far as I can see, there currently is no KMS support. Unfortunately this blocks us from using this service due to regulations. Is there a timeline for supporting KMS? Thanks Jonas

Hi, The quotas page specifies a limit of 20 brokers per account per region: https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-limits.html Does an active/standby broker count as 1 or 2 brokers regarding this limit?

I'm trying to figure out if using a network of brokers will solve some of the problems I'm having with single-instance and active-standby brokers. With a network of brokers, - can a client use one URL to connect to the network of brokers, or would the client need to potentially try separate URLs for each broker in the network? - Amazon has started making noise about instituting a limit on the number of connections a given broker can have open at a given time - does that limit go up if that broker is part of a network? - if using a network of single-instance brokers, would an automatic failover work the same way as it does for active-standby pairs?