# AWS permission problem in Lambda

**URL:** <https://forum.serverless.com/t/aws-permission-problem-in-lambda/9247>\
**Category:** Serverless Framework\
**Tags:** aws, iam\
**Created:** [September 8, 2019, 12:31am UTC](https://forum.serverless.com/t/aws-permission-problem-in-lambda/9247 "2019-09-08T00:31:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lost\_in\_space](https://avatars.discourse-cdn.com/v4/letter/l/a88e57/32.png) [@lost\_in\_space](https://forum.serverless.com/u/lost_in_space)\
**Post date:** [September 8, 2019, 12:31am UTC](https://forum.serverless.com/t/aws-permission-problem-in-lambda/9247/1 "2019-09-08T00:31:25Z")

</div>

I am scratching my head on a permission issue. I am using a named AWS profile to deploy and have no problem in this. IAM permissions are all ok and I have even tried setting the user to a full administrator in an attempt to figure this out.

The problem is that access to services (specifically in this case SQS) is giving a permission error. If, however, I do an aws config update in the lambda function with the same access key and secret that is being used to deploy there is no problem.

Environment: MacOS latest

IAM role statement is sqs:\* on all resources

Has anyone seen this before and do they have any suggestions?