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
After deploying, sending a message always throws an access denied error (error: AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com/ is denied):
Full error:
{ value: { error: AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com/ is denied. at Request.extractError (/opt/nodejs/node_modules/aws-sdk/lib/protocol/query.js:50:29) at Request.callListeners (/opt/nodejs/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/opt/nodejs/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/opt/nodejs/node_modules/aws-sdk/lib/request.js:686:14) at Request.transition (/opt/nodejs/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/opt/nodejs/node_modules/aws-sdk/lib/state_machine.js:14:12) at /opt/nodejs/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/opt/nodejs/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/opt/nodejs/node_modules/aws-sdk/lib/request.js:688:12) at Request.callListeners (/opt/nodejs/node_modules/aws-sdk/lib/sequential_executor.js:116:18) { code: 'AccessDenied', time: 2022-06-28T16:37:44.889Z, requestId: '09a7e81d-722b-56b8-8601-b32842b3e67a', statusCode: 403, retryable: false, retryDelay: 91.4007833446157 } } }
raiseandfall
changed the title
SQS Access Denied to
AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com is denied
Jun 28, 2022
raiseandfall
changed the title
AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com is denied
AccessDenied to resource https://sqs.us-east-1.amazonaws.com
Jun 28, 2022
raiseandfall
changed the title
AccessDenied to resource https://sqs.us-east-1.amazonaws.com
Queue: AccessDenied to resource https://sqs.us-east-1.amazonaws.com
Jun 28, 2022
First I thought that my existing IAM Role Statement on the publish handler was overwriting the SQS one, but even when commenting out the whole iamRoleStatements block I'm still getting the AccessDenied issue.
It's working now, but it would be interested to figure out why the permission are not set automatically, as specified in the doc.
Description
After deploying, sending a message always throws an access denied error (
error: AccessDenied: Access to the resource https://sqs.us-east-1.amazonaws.com/ is denied
):Full error:
How to Reproduce
serverless.yml
handlers.yml
Please note that
publisherHandler
also invoke another lambda, thus the iam role therepublisherHandler.ts
Additional Information
3.17.0
1.19.0
QueueUrl
has the right value in the publisher handlerThere is obviously a permission issue, but I can't figure out what.
The text was updated successfully, but these errors were encountered: