Hi Jay, as Phil said we haven’t purposely configured anything to avoid this, and haven’t seen this issue when connecting to a R53 private zone CNAME using clients for SSL and STOMP-SSL on 3 different languages.
Out of curiosity, are you using public or private DNS?
It seems that you are not the only one having this issue. If you look at the last message on this AMQ forum post, it seems like the exact same one:
Maybe it’s worth asking AWS support via the forums or a ticket? I’d be curious to know their answer. It will be great if friendly CNAMES were natively supported, or at least more static like for example RDS.