-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
SQS_AWS_REGION is ignored #859
Comments
It also looks like |
Hey, first of all, thanks for raising this issue :)
Can you elaborate, how you discovered that it is broken? Could you not create SQS queues? I could not reproduce it with the latest version. But i recognized that the UI initially shows, that default was
How do you recognize that? What is not working? |
Hi,
At this point, the sqs admin UI shows no queues and defaults to the message I mentioned above which caused the confusion. Trying to diagnose further, when I run aws local to list the queues I can see it being returned. Just not from the admin container. Yeah I agree - would definitely be helpful to see more info from the logs :) Really appreciate this. |
thanks to @bhavishyachandra this is now solved |
Hi,
It looks like a recent update broke the ability to configure the AWS region where the environment variable
SQS_AWS_REGION
is ignored. I pulled the latest contain and it defaults toeu-central-1
ignoring what i have set in the docker compose file.The text was updated successfully, but these errors were encountered: