Open mcandio opened 4 months ago
@mcandio Hi, I guess you get some trouble about IAM. To be frank, IAM support is not fully tested before. We need some time to verify.
I am curious about this message
[error="Get \"http://169.254.169.254/latest/meta-data/iam/security-credentials/\": dial tcp 169.254.169.254:80: connect: host is down"]
Have you check your IAM server?
@mcandio Hi, I guess you get some trouble about IAM. To be frank, IAM support is not fully tested before. We need some time to verify. I am curious about this message
[error="Get \"http://169.254.169.254/latest/meta-data/iam/security-credentials/\": dial tcp 169.254.169.254:80: connect: host is down"]
Have you check your IAM server?
Hi @wayblink , sorry for the late response.
connect: host is down"
show up because the my localhost is not an AWS server.
The server is running and in fact, it works if I try to run the backup tool from an aws instance that has the instance metadata available at 169.254.169.254.
This error is showing when I run the backup tool locally, with exported AWS envs like:
export AWS_ACCESS_KEY_ID=<redacted>
export AWS_SECRET_ACCESS_KEY=<redacted>
export AWS_SESSION_TOKEN=<redacted>
This behaviour is not only limited to these exported env vars, the tool is not recognising the .aws/config params too. it is only trying to fetch the metadata and make use of it but of course, it is not there.
If you have any insight about this, it would be great, we ended up creating a big python API to handle backups but we need to understand what is the expected behaviour. Thanks!
Current Behavior
My current milvus infrastructure is: eks helm standard deployment with IRSA role I use s3 as the storage endpoint seems like the tool is not able to use exported aws credentials or the config file even if useiam is specified. i am running :
kubectl -n stride-tutoring port-forward --address 0.0.0.0 service/milvus-default 19530:19530
and I have also configured an ingress, when I use a jumphost with a role attached, the tool is able to run smoothly, but when I try to use my local computer, it is not working by exporting the env vars, (secret key, keyid, token)my config file:
It is also not working if I use the following config file and if I export my aws envs:
the error is:
can someone help me understand the default behaviour when no instance role is attached? I mean when assuming role or using local aws credentials? this approach also does not work when using .aws/credentials file
thanks!