Gave a user full access to SQS but it can still access absolutely no data

0

I created a new user and assigned it the following policy:

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"sqs:DeleteMessage",
"sqs:GetQueueUrl",
"sqs:ListQueues",
"sqs:ChangeMessageVisibility",
"sqs:SendMessageBatch",
"sqs:UntagQueue",
"sqs:ReceiveMessage",
"sqs:SendMessage",
"sqs:GetQueueAttributes",
"sqs:ListQueueTags",
"sqs:",
"sqs:TagQueue",
"sqs:ListDeadLetterSourceQueues",
"sqs:DeleteMessageBatch",
"sqs:PurgeQueue",
"sqs:DeleteQueue",
"sqs:CreateQueue",
"sqs:ChangeMessageVisibilityBatch",
"sqs:SetQueueAttributes"
],
"Resource": "
"
}
]
}

I also gave it access to 'all resources' instead of a specific ARN

However, if I try to get the list of queues, I see one which I don't recognize, and if I try to directly view one of my SQS queues by getting its attributes, it tells me I don't have access to it.

Any ideas what I did wrong..? May be because of that one unknown queue, its pulling from somewhere else instead of my account's queues?

질문됨 5년 전191회 조회
1개 답변
0

Turns out the default credentials were not being read from the environment variables as the documentation promised. Providing them specifically using the static credentials provider fixed this issue.

답변함 5년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠