# AWS hivemq scale **URL:** \ **Category:** Uncategorized\ **Created:** [October 13, 2022, 6:40am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520 "2022-10-13T06:40:03Z")\ **Posts on this page:** 15\ **Page:** 2
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 17, 2022, 1:50am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/22 "2022-10-17T01:50:31Z")
hi michael, after changing the propoties file I think everything works well now, they found each other ```auto 2022-10-17 01:48:37,637 INFO - Cluster size = 2, members : [dspm6, e69ds]. 2022-10-17 01:48:37,638 DEBUG - Sending RUNNING state notification for dspm6 to all nodes. 2022-10-17 01:48:37,640 DEBUG - Removing redundant persistence entries after join 2022-10-17 01:48:37,658 DEBUG - Removed redundant persistence entries after join in 17ms 2022-10-17 01:48:39,616 DEBUG - Reading properties file '/opt/hivemq/extensions/hivemq-s3-cluster-discovery-extension/s3discovery.properties'. 2022-10-17 01:48:39,917 DEBUG - Found following node addresses with the S3 extension: [172.31.44.31:7800, 172.31.47.49:7800] ``` ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 17, 2022, 2:14am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/23 "2022-10-17T02:14:46Z")
Hi Michael Sorry for the flooding messages, just got some questions related to the test. 1. I’ve successfully connected to the load-balancer DNS name by using the node-red service, Just want to know how can I assess the HiveMQ control center? using DNSname:8080? that doesn’t work 2. for the published topics, in the s3 bucket, am I able to see the data that was published? each publish message was a set of timestamps and messages, for now, I can only see them in the node-red debug window. 3. for the load balancer, will the instance scale up or scale down? if not, how can I make them scale up and scale down depending on the requirements? looking forward to your reply Best Regards, Jeffrey Lin ---
**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\ **Post date:** [October 17, 2022, 8:32am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/24 "2022-10-17T08:32:24Z")
Hi @jeffrey, I was wondering what you meant with `hivemq-s3-cluster-discovery-extension.xml` as the S3 extension only had `s3discovery.properties`. Seems the blog post had outdated information, this will be fixed. > I’ve successfully connected to the load-balancer DNS name by using the node-red service, Just want to know how can I assess the HiveMQ control center? using DNSname:8080? that doesn’t work You also need to add the port of the Control Center to the Load Balancer. My guess is your Load Balancer has only this set of listener: ![Bildschirmfoto 2022-10-17 um 10.19.39](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/403fa9ed09c95a9bea90c6165dfc2376d0aa17e9.png) You click “Edit” and add a listener for your Control Center (according to config.xml port is 8080): ![Bildschirmfoto 2022-10-17 um 10.20.08](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/f0d423613197fddd0824f6197ed4a86dcf88ed6a.png) Make sure you have sticky session enabled, you can do this in the “Description” menu of the Load Balacner: ![Bildschirmfoto 2022-10-17 um 10.24.28](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/c57a43ef0fd71f04459a3c02b878d7e5b05a465c.png) > for the published topics, in the s3 bucket, am I able to see the data that was published? each publish message was a set of timestamps and messages, for now, I can only see them in the node-red debug window. The s3 extension is only used so that the HiveMQ instances can discover each other and form a cluster. HiveMQ will not do anything else with the s3 bucket, hence the name `hivemq-s3-cluster-discovery-extension`. > for the load balancer, will the instance scale up or scale down? if not, how can I make them scale up and scale down depending on the requirements? So as the blog post mentions at the end, currently you would have to do this manually by creating (+configuring)/deleting instances and adding/removing them in the “Target Group” so you can scale up/down. > For production environments it’s recommended to use automatic provisioning of the EC2 instances (e.g. by using Chef, Puppet, Ansible or similar tools) so you don’t need to configure each EC2 instance manually. Of course HiveMQ can also be used with Docker, which can also ease the provisioning of HiveMQ nodes. Greetings, Michael ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 17, 2022, 9:09am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/25 "2022-10-17T09:09:52Z")
Hi Michael there’s no http option in my load balancer ![image](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/347409e1b21a2a075cc73c7860135d2afd58422f.jpeg) ---
**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\ **Post date:** [October 17, 2022, 10:52am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/26 "2022-10-17T10:52:27Z")
Hi @jeffrey, Found the issue, I used an existing “Classic” load balancer(LB) to show you how to create a HTTP listener, whereas you have an “Network Load Balancer”. So I’m not sure what Amazon recommends as best practice in the case you need a TCP and HTTP listener. The options I see: 1. Use an classic load balancer and add listener for both ports (MQTT + Control Center) 2. Use an application load balancer to expose the Control Center and a network load balancer to expose MQTT If you currently are only testing out HiveMQ I would say delete the Network LB and create an Classic LB instead and add the TCP + HTTP listener to it. Note 1: This one you can try out before doing anything else, maybe it is enough to add a TCP\_UDP listener that forwards on 8080 to 8080 (don’t forget to enable sticky session). Note 2: The Classic Load Balancer is a folded menu in “Select load balancer type” Hope this helps, Michael ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 17, 2022, 12:06pm UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/27 "2022-10-17T12:06:41Z")
for the initial load balancer ![image](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/db0c319cb494eabdb561ad393f26b2059d05f6a2.jpeg) ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 17, 2022, 12:07pm UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/28 "2022-10-17T12:07:55Z")
![image](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/fb87724d221da49bfd7c8b0b1d6cedcf5bb20a93.png) this is the new classic LB but when I try to use DNS name:8080 to access the control centre that doesn’t works ---
**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\ **Post date:** [October 17, 2022, 12:56pm UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/29 "2022-10-17T12:56:18Z")
I don’t see more config options and it works here, so let’s debug why it doesn’t work for you: - You added the instances as target group to the Classic Load Balancer? You should see them in the “Instances” menu from the Load Balancer - Does the MQTT forwarding still work? - 8080 is your configured port for the Control Center right? ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 18, 2022, 10:58am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/30 "2022-10-18T10:58:30Z")
![image](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/a62a234a32e4dc4159a5407c4a029c681947b705.png) hi Michael, in the article they didn’t configure the port 8080 ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 18, 2022, 11:03am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/31 "2022-10-18T11:03:26Z")
in the config.xml file, I see the control center listeners on port 8080, so I think there’s something wrong in the article ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 18, 2022, 11:12am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/32 "2022-10-18T11:12:02Z")
sorry again for the flooding message, the community doesn’t allow me to reply with multiple images, when I try to change the security group inbound rule, if I change the port to 8080, it’s still TCP protocol, if I change the type to “HTTP”, the protocol still TCP and I cannot change the port range to 8080, it’s fix to port 80 ![image](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/846ef26d2aa8c8d54ffddd1ed4b97f1cdc09ba42.png) ---
**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\ **Post date:** [October 18, 2022, 11:25am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/33 "2022-10-18T11:25:11Z")
Yes this makes sense as the article only describes how to create a load balancer for the MQTT traffic, the Control Center isn’t covered in the article. I see we use Custom TCP in the inbound rule for the Control Center: ![Bildschirmfoto 2022-10-18 um 13.22.54](https://canada1.discourse-cdn.com/flex035/uploads/hivemq1/original/1X/63f4b14cd7ee7554057b64928bc30c017150c20c.png) Might want to try that. Greetings, Michael ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 18, 2022, 11:38am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/34 "2022-10-18T11:38:36Z")
Perfect Michael, much appreciate your patient reply which really helps a lot! now the control center is working! BTW, I’m curious what is the maximum request these two cluster nodes can handle? in other words, How many publishers/subscribers can those two nodes handle while maintaining the integrity and speed of the transmitted message? ---
**Author:** ![michael\_w](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/michael_w/32/200_2.png) [@michael\_w](https://community.hivemq.com/u/michael_w)\ **Post date:** [October 18, 2022, 11:54am UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/35 "2022-10-18T11:54:54Z")
I’m glad it finally works 🥳 > BTW, I’m curious what is the maximum request these two cluster nodes can handle? in other words, How many publishers/subscribers can those two nodes handle while maintaining the integrity and speed of the transmitted message? Ah I “hate” this question! Because it’s always hard to answer because it most often depends on the use case and on the hardware (basically this is what our customer success team is for and not the community forum). At least I can say: It shouldn’t be a problem to have 6 figures amounts of clients connected simultaneously. Greetings, Michael ---
**Author:** ![jeffrey](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jeffrey](https://community.hivemq.com/u/jeffrey)\ **Post date:** [October 18, 2022, 12:58pm UTC](https://community.hivemq.com/t/aws-hivemq-scale/1520/36 "2022-10-18T12:58:07Z")
hahah Got it! Thanks Michael, really appreciate it!! [Previous page](https://community.hivemq.com/t/aws-hivemq-scale/1520.md?page=1)