AWS addon fails when using IMDSv2

As part of AWS best practice we run EC2 instances with IMDSv2 enforced. The AWS addon fails when using IMDSv2 with an error:

openvpn3-service-aws[1354]: /usr/lib/x86_64-linux-gnu/openvpn3-linux/openvpn3-service-aws: Error preparing route context: Error preparing route context: could not fetch AWS identity document: GET http://169.254.169.254/latest/dynamic/instance-identity/document : 401 Unauthorized

Is it possible to add IMDSv2 support?

[lstipakov]

Sorry for delay and thanks for letting us know. Let me reproduce the problem first.

[lstipakov]

Managed to reproduce the problem, I am on it.

[lstipakov]

@mattjbyrd I have pushed fixes (there were two issues with AWS addon) to my fork. The problems were in openvpn3-core, not in openvpn3-linux. Would you be able to build the Linux client on your own (pointing openvpn3-core submodule to my fork) and verify that it works for you?

Apologies for the delay. Yes, will get this tested :)

@lstipakov can confirm that it now works with IMDSv2 using your fork.

[dsommers]

This should be resolved with commit 90b07a2, which will be included in v21. This ticket will be closed when v21 is released.