I have been exploring boundary and running them on dev mode in an aws ec2 instance and dynamically targeting other ec2 hosts by applying a filter as here-https://github.com/hashicorp/boundary-plugin-host-aws
These hosts that gets created of the dynamic host sets don’t display the private IP address on the boundary app which makes it impossible to know the identity of the host. (Refer Snip 1)
Also, when connecting to these dynamic hosts, the cli defaults the ssh connection to he private dns of the hosts and not the IP address of the host.
Also when looking from the controller console, dynamic host source for targets has type "Missing translation “resources.host-set.types.plugin” for locale “en-us” - Refer Snip2
Am I wrongly configuring the dynamic host sets or is there something I am missing in here.
Note - Although when the hosts are read using the cli, ip’s do get displayed, but not on the console.