It seems that it has introduced a regression bug 2179718.
VERIFIED using NetworkManager-1.43.6-1.el9: Token is acquired: [Request URI: http://169.254.169.254/latest/api/token] File Data: 56 bytes Data (56 bytes) 0000 41 51 41 41 41 4c 48 2d 6b 37 69 31 38 4a 4d 6b AQAAALH-k7i18JMk 0010 4b 2d 4f 52 4c 5a 51 66 41 61 37 6e 6b 4e 6a 51 K-ORLZQfAa7nkNjQ 0020 62 4b 77 70 51 50 45 78 4e 48 71 7a 6b 31 6f 4c bKwpQPExNHqzk1oL 0030 5f 37 65 68 2d 41 3d 3d _7eh-A== And then used: Hypertext Transfer Protocol GET /2018-09-24/meta-data/network/interfaces/macs/ HTTP/1.1\r\n [Expert Info (Chat/Sequence): GET /2018-09-24/meta-data/network/interfaces/macs/ HTTP/1.1\r\n] [GET /2018-09-24/meta-data/network/interfaces/macs/ HTTP/1.1\r\n] [Severity level: Chat] [Group: Sequence] Request Method: GET Request URI: /2018-09-24/meta-data/network/interfaces/macs/ Request Version: HTTP/1.1 Host: 169.254.169.254\r\n Accept: */*\r\n X-aws-ec2-metadata-token: AQAAALH-k7i18JMkK-ORLZQfAa7nkNjQbKwpQPExNHqzk1oL_7eh-A==\r\n \r\n [Full request URI: http://169.254.169.254/2018-09-24/meta-data/network/interfaces/macs/]