operation error Elastic Load Balancing v2: DescribeLoadBalancers, get identity: get credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, canceled, context deadline exceeded

[g-bohncke]

Describe the bug
A concise description of what the bug is.

When running the latest version chart 1.10.1 app version : v2.10.1 we are encountering:
the following error.

operation error Elastic Load Balancing v2: DescribeLoadBalancers, get identity: get credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, canceled, context deadline exceeded.

this seems to be related to the change to AWS SDK Go v2 version and looks like the code ignores the vcpId and region from the helm chart. "Instead of depending on IMDSv2, you can specify the AWS Region and the VPC via the controller flags --aws-region and --aws-vpc-id." the SDK looks to be always pulling the metadata. cloud.go

Steps to reproduce
install the latest version on a private cluster.

Expected outcome
A concise description of what you expected to happen.
That the service works

Environment

• AWS Load Balancer controller version
  v2.10.1
• Kubernetes version
  1.29
• Using EKS (yes/no), if so version?
  Yes 1.29

Additional Context:

• the latest policy has been applied and we use the policy via the node. (option B according to the docs).
• we already verified that all the instances have a hop count of 2.

[shraddhabang]

Hey @g-bohncke , If you look here, we always infer the vpc-id and region from config first if its set before we infer it from ec2metadata. So it should have worked for you. Can we know which helm flags are using to set these values?