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

Question

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?

Answer

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.

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

Relevant content