I am not sure if anyone else has encountered this but it seems AWS IMDSv2 is not currently supported by MultiCloud/Agent (Explanation around IMDSv1 vs IMDSv2 but the gist is IMDSv1 is no-authentication metadata retrieval and what the agent currently uses to “identify” a machine as AWS instance and pull the InstanceID which then MultiCloud correlates to the Proxy record based on; IMDSv2 is token-based-athetication metadata retrieval and IF enabled client just doesn’t see the machine as AWS instance at all, so MultiCloud never correlates - proxy and native record just sit unrelated to one another forever). By definition IMDSv2 is a lot more secure, so we naturally want/are starting to use it but it will break ALL AWS correlations once fully enabled…
Anyway, submitted an RFE and if you think that it may be something that you’d need please vote, and hopefully it will get fixed asap.