read: connection reset by peer with 169.254.76.1 IP address

[djacquensf9]

Hi,

I tried a few times using this very useful extension but I got an weird error using "arn:aws:lambda:eu-west-1:634166935893:layer:vault-lambda-extension:14"

I created a new Python lambda in one my VPC (CIDR 10.25.0.0/16) with two subnets (10.25.0.0/24 & 10.25.1.0/24)

I check that the lambda has an ENI in each subnet (10.25.0.252 & 10.25.1.185)

When I run the lambda, I get this error:

{
  "errorType": "Extension.Crash",
  "errorMessage": "RequestId: de1ec900-5c40-4613-b332-1234564894d Error: exit status 1"
}

Function Logs
2023-02-27T08:42:30.644Z [INFO]  vault-lambda-extension: Initialising
2023-02-27T08:42:30.651Z [ERROR] Fatal error, exiting: error="error logging in to Vault: read tcp 169.254.76.1:60942->10.25.1.155:8200: read: connection reset by peer"
EXTENSION	Name: vault-lambda-extension	State: Started	Events: []
2023-02-27T08:42:32.357Z [INFO]  vault-lambda-extension: Initialising
2023-02-27T08:42:32.437Z [ERROR] Fatal error, exiting: error="error logging in to Vault: read tcp 169.254.76.1:60954->10.25.1.155:8200: read: connection reset by peer"
EXTENSION	Name: vault-lambda-extension	State: Started	Events: []
START RequestId: de1ec900-5c40-4613-b332-1234564894d Version: $LATEST
RequestId: de1ec900-5c40-4613-b332-1234564894d Error: exit status 1
Extension.Crash
END RequestId: de1ec900-5c40-4613-b332-1234564894d
REPORT RequestId: de1ec900-5c40-4613-b332-12345654894d	Duration: 1698.82 ms	Billed Duration: 1699 ms	Memory Size: 128 MB	Max Memory Used: 24 MB

I don't pass the python code of the lambda because if I am not mistaken the lambda crashes when running the layer.
I don't understand why the request is done from the reserved IP 169.254.76.1?
What info do you need?
What have I done wrong?

Thanks, 😉

David