-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
Aws::SQS::Errors::AccessDenied from Shoryuken::CLI #339
Comments
Hi @parov I've only used Do you have your AWS keys exported? |
Nope, I use IAM only. |
@parov hm this Could you try |
The required permissions: https://github.com/phstc/shoryuken/wiki/Amazon-SQS-IAM-Policy-for-Shoryuken |
Same issue with
|
hi @parov I'm having hard to time figure this out. Both No clue yet, but I will keep digging. |
@parov problem solved. All theses commands should be working fine in 3.0.3. Could you let me know if they work for you? |
Use `get_queue_url` to get a single queue URL Fix #339
@parov I wasn't thinking much on using it from a controller. I actually, don't even SSH for using it, I have a special user with write privileges that I use for write operations: ce pablo_admin # login with write privileges
(pablo_admin) bundle exec shoryuken sqs mv ...
exit # logout My setup: # ~/.zshrc
# aws-vault https://github.com/99designs/aws-vault
alias ce='aws-vault exec -n'
function ce_prompt () {
if [[ -n "$AWS_VAULT" ]]
then
echo "($AWS_VAULT) "
fi
}
PROMPT='$(ce_prompt) ...' But if you do want to run it from a Rails controller, we may subprocess, WDYT? system('bundle exec shoryuken ...') |
So, the reason to have it in a controller is for me only to move back jobs from a dead letter queue.
Subprocessing looks cleaner, but probably it's not needed here |
@parov I replied you in the PR https://github.com/phstc/shoryuken/pull/342/files#r107178275 |
Hi,
I'm trying to use the new CLI amazing feature you build, but when running it from the console I get
Aws::SQS::Errors::AccessDenied from Shoryuken::CLI
. Looks likeAws::SQS::Client.new
, but when callingcli.mv old_queue new_queue
the exception is appearing.Shoryuken works already pretty well with AWS IAM, but for some reasons the CLI don't.
I tried also to add it in a Controller and run it from there, with the same result.
Do I need some extra setup to make it work?
Thanks for the amazing job
The text was updated successfully, but these errors were encountered: