You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation for both the sqs input and output plugins provide a sample IAM policy document which is missing Action keys listed directly above it in the docs:
The "consumer" identity must have the following permissions on the queue:
sqs:ChangeMessageVisibility
sqs:ChangeMessageVisibilityBatch
sqs:DeleteMessage
sqs:DeleteMessageBatch
sqs:GetQueueAttributes
sqs:GetQueueUrl
sqs:ListQueues
sqs:ReceiveMessage
yet the sample policy is missing DeleteMessage and DeleteMessageBatch:
There is a similar issue in the output plugin which I will open seperately, and imo an issue with the error handling of AccessDenied errors, since logstash doesnt log which action is attempting to be done, and Cloudtrail doesnt log SQS API calls.
Feb 02 18:27:11 ip-10-202-5-90 logstash[410]: {:timestamp=>"2017-02-02T18:27:11.273000+0000", :message=>"Aws::SQS::Errors::ServiceError ... retrying SQS request with exponential backoff", :queue=>"logstash_logs_us-west-1_staging_logstash-test-emitter", :sleep_time=>1, :error=>#<Aws::SQS::Errors::AccessDenied: Access to the resource https://sqs.us-west-1.amazonaws.com/[REDACTED]/logstash_logs_us-west-1_staging_logstash-test-emitter is denied.>, :level=>:warn}
The text was updated successfully, but these errors were encountered:
Hrm, I was mistaken about the output plugin, the documentation matches there. However, I still think the error handling in bad IAM case could use improvement judging by logstash-plugins/logstash-output-sqs#17
nhumphreys
added a commit
to nhumphreys/logstash-input-sqs
that referenced
this issue
Nov 16, 2017
The documentation for both the sqs input and output plugins provide a sample IAM policy document which is missing Action keys listed directly above it in the docs:
yet the sample policy is missing DeleteMessage and DeleteMessageBatch:
There is a similar issue in the output plugin which I will open seperately, and imo an issue with the error handling of AccessDenied errors, since logstash doesnt log which action is attempting to be done, and Cloudtrail doesnt log SQS API calls.
The text was updated successfully, but these errors were encountered: