Improvement to Amazon MQ - export instances IP addresses to allow ELB creation

[nestorbolivar]

Hi There,

It would be great to export Amazon MQ instances IDs or IP addresses. We could create ELBs placed in public subnets and redirect them to the admin consoles.

Cheers,
Nestor

[loivis]

I think AWS doesn't expose such info, at least not in DescribeBrokerResponse? BrokerInstance has only attributes as ConsoleURL and Endpoints, which are already exported.

[nestorbolivar]

@loivis I'm getting the 'Endpoints' ip addresses using the dns data provider. Then I associate an ELB to those IP addresses... It would be great if it could be handled as part of the MQ data source. e.g. primayMQendpointIP & secondaryMQendpoint ... ;)

[nestorbolivar]

I get the IP address as follows;

data "dns_a_record_set" "elb1" {
  count = "${var.enable_aamq == "True" ? 1 : 0}"
  host = "${aws_mq_broker.lp_aamq_brk.id}-1.mq.${var.aws_region}.amazonaws.com"
}

This os for the target group:

resource "aws_lb_target_group_attachment" "mq_ip_attach_1" {
  count = "${var.enable_aamq == "True" ? 1 : 0}"
  depends_on = ["aws_mq_broker.lp_aamq_brk"]
  target_group_arn = "${aws_lb_target_group.aamq_elb_tg.arn}"
  target_id        = "${data.dns_a_record_set.elb1.addrs[0]}"
  port             = 8162
}

[loivis]

In you case, I think it's reasonable that terraform ouputs hostname attributes for mq_broker. Then you don't need to concatenate strings to get the hostname. But dns_a_record_set data source is still need to get ip from hostname. IMPO, I don't think terraform should do this dns lookup.

[loivis]

Seems like it's possible to query eni to get those IPs. AWS is following the similar rule as elb to have mq id within description.

[bflad]

The ip_address attribute inside instances has been exposed via #6103 and released in version 1.40.0 of the AWS provider last week. Please reach out if this is not what you were looking for here.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!