Custom domain for publicly available Amazon MQ (Rabbit MQ) Web Console

0

Hello,

I've been trying to set up a memorable URL for our RabbitMQ web console (publicly available, cluster deployment), so that our team can easily access it. Things I've tried:

  • Add an application load balancer in front of the console, which doesn't work because I don't have access to the IP addresses of the RabbitMQ service
  • Add a CNAME pointing to the Web Console, which also doesn't work because the certs on the deployed web console do not match the certs used for our domain

Is there anything else I can try?

2 Risposte
0

Hi,

Private or Public AmazonMQ broker IPs stay the same for either ActiveMQ or RabbitMQ until you delete the broker. Broker architecture.

Although RabbitMQ does not show its IP addresses, you can reliably find its VPC endpoints by querying the broker DNS records (nslookup or host) and use them to setup your load balancer.

This blog might be sufficient for your use case: https://aws.amazon.com/blogs/compute/creating-static-custom-domain-endpoints-with-amazon-mq-for-rabbitmq/

AWS
TECNICO DI SUPPORTO
kgopelo
con risposta 2 anni fa
  • I have not been able to do so:

    ~/p/e/nxtp ❯❯❯ nslookup b-8e091635-08a4-4bd0-856c-aefadfa2fb07.mq.us-west-1.amazonaws.com                                                                                                    
    Server:         192.168.0.1
    Address:        192.168.0.1#53
    
    Non-authoritative answer:
    b-8e091635-08a4-4bd0-856c-aefadfa2fb07.mq.us-west-1.amazonaws.com       canonical name = rabbit-broker-aefadfa2fb07-180be1c36dfa0147.elb.us-west-1.amazonaws.com.
    Name:   rabbit-broker-aefadfa2fb07-180be1c36dfa0147.elb.us-west-1.amazonaws.com
    Address: 54.67.47.83
    Name:   rabbit-broker-aefadfa2fb07-180be1c36dfa0147.elb.us-west-1.amazonaws.com
    Address: 52.52.45.254
    

    These IP addresses returned are not valid as LB targets it seems. How else can I proceed?

    As I mentioned, I only need the RabbitMQ Management dashboard to have a custom domain

0

There is a blog post Creating static custom domain endpoints with Amazon MQ to simplify broker modification and scaling that talks about setting up a custom domain for Amazon MQ. It uses NLB to host a custom domain. Hope this helps.

AWS
Taka_M
con risposta 2 anni fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande