-
-
Notifications
You must be signed in to change notification settings - Fork 138
Credentials expiration using InstanceProvider and SQS #1634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, Just checking in on this. Any updates? Thanks! Pierre |
Up |
I wanted to kindly follow up on this issue. Is there any update or further information needed to move forward? Thank you for your time and support! |
I can't reproduce the issue, from the source code, we are using the expiration date provided by AWS to evict the cached (30 seconds before the expiration). Could you add logs in your application to assert the |
Hello,
|
I've also been experiencing this issue. It doesn't happen often, only 12 times in the last 90 days, but the service that's pushing to that queue can't miss events, or it might cause downstream issues
The service is using AWS ECS Fargate instances using supervisor to run the queue. Each messenger queue consumes 10 messages before restarting, so this is variable in how often it restarts. I will keep investigating to see if I can find more information. |
Hello,
Thank you for your great packages! 😄
I'm using Symfony 5.4 along with the Messenger component, which includes the
async-aws/core
andasync-aws/sqs
packages. Our integration is configured to connect using the AWS Identity and Access Management (IAM) instance profile, which is valid for up to six hours.My workers are managed by supervisord with a 3600-second time limit, after which the workers are automatically restarted.
Credentials are loaded when the worker starts, but if the credentials expire before the end of the worker's time limit, I encounter this error:
I checked the AWS documentation and found this:
Is there a way to automatically rerun the authentication if the
Expiration
time plus 5 minutes is greater than the current datetime, without having to restart my workers?The text was updated successfully, but these errors were encountered: