Fixes https://github.com/JuliaCloud/AWS.jl/issues/654, mitigates #651, and modifies PR https://github.com/JuliaCloud/AWS.jl/pull/650 to no longer report the ETIMEOUT as a connection error. It turns out that particular error indicates that the IMDSv2 PUT request for a token has reached the max hop limit and the server is rejecting the packet. This PR updates the IMDS code to classify this error as a TTL expiration and fall back to using IMDSv1 rather than treating the IMDS service as being unavailable.
Fixes https://github.com/JuliaCloud/AWS.jl/issues/654, mitigates #651, and modifies PR https://github.com/JuliaCloud/AWS.jl/pull/650 to no longer report the
ETIMEOUTas a connection error. It turns out that particular error indicates that the IMDSv2 PUT request for a token has reached the max hop limit and the server is rejecting the packet. This PR updates the IMDS code to classify this error as a TTL expiration and fall back to using IMDSv1 rather than treating the IMDS service as being unavailable.The TTL timeout is rather slow so users should consider increasing their hop limit in order to allow IMDSv2 to be used in these scenarios. I'll add a warning to inform users of this