New bootstrap_brokers_attached_enis output for aws_msk_cluster

[e-moshaya]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

I am Trying to integrate MSK with NLB for privatelink connectivity using the steps laid out here. This requires me to add each Kafka broker ip address to the NLB target group. For that to work, I will need to get the attached eni id for each broker which is available in the AWS Console via the broker details section.

New or Affected Resource(s)

• aws_msk_list_nodes

Potential Terraform Configuration

resource "aws_msk_list_nodes" "example" {
  cluster_arn           = aws_msk_cluster.example.arn
}

References

• https://aws.amazon.com/blogs/big-data/how-goldman-sachs-builds-cross-account-connectivity-to-their-amazon-msk-clusters-with-aws-privatelink/

[e-moshaya]

On second thoughts, I think the list nodes data resource is what we need. Here is the CLI equivalent https://docs.aws.amazon.com/cli/latest/reference/kafka/list-nodes.html

[ewbankkit]

@e-moshaya Thanks for raising this issue.
It has already been noticed in #11085. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue.
Please add any additional comments there.

Actually this isn't identical to #11085 (that issue is about broker node IP addresses) although it is similar.
It looks like #20615 will address this.

[github-actions]

This functionality has been released in v3.60.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.