> But such a feature could also be used to create a fake 169.254.169.254 (AWS/Cloud metadata IP address endpoint) and serve requests from it.
Wouldn’t such a thing be impossible if the application is using end-to-end encrypted requests to AWS?
> But such a feature could also be used to create a fake 169.254.169.254 (AWS/Cloud metadata IP address endpoint) and serve requests from it.
Wouldn’t such a thing be impossible if the application is using end-to-end encrypted requests to AWS?