token is not refreshed when running in k8s pod connected to serviceaccount about mountpoint-s3 HOT 8 OPEN

Can you please share the logs around the time mount-s3 loses access to the s3 bucket. What is the error that you receive? Thanks.

from mountpoint-s3.

i don't have the logs anymore, but i received an http 403 error
if you really need them i can probably simulate it again

from mountpoint-s3.

Yes. Could you please simulate it again, and provide the logs?
Please run mount-s3 with --debug CLI flag. You can check more details on logging at our logging page.

from mountpoint-s3.

Hey @coolstim. Please use the --debug-crt flag as well as --debug. This will provide us with more detail on what the underlying AWS Common Runtime (CRT) client is doing and if it attempts to renew the token.

from mountpoint-s3.

atm we abandoned the use of mountpoint-s3 because of performance issues, we now use lustre fsx with a data repository association to s3 which performs a whole lot better.
If we ever get back to this i will rerun the it with the given flags and post my findings here

from mountpoint-s3.

Glad you were able to move forward for your use case. I do want to make sure we solve this issue for anyone else who may face it, so I will leave this open for now and we'll investigate further on our side.

mount-s3 loses access to the s3 bucket when the process runs longer than the token expiration time.

Are you able to confirm which token you believed was expiring? Was it the web identity token, the IAM session, or unclear?

from mountpoint-s3.

unclear tbh

from mountpoint-s3.