I am facing the same issue. Tried with versions 2.29.0, 2.31.0 and the ci/cd feature on serverless.com.
The error message when running “serverless deploy --debug”
NoSuchEntity: Policy arn:aws:iam::aws:policy/AWSLambdaFullAccess does not exist or is not attachable.
at Request.extractError (/var/task/node_modules/aws-sdk/lib/protocol/query.js:50:29)
at Request.callListeners (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/task/node_modules/aws-sdk/lib/request.js:688:14)
at Request.transition (/var/task/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/task/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/task/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/var/task/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/var/task/node_modules/aws-sdk/lib/request.js:690:12)
at Request.callListeners (/var/task/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
I have the same issue when try to deploy a new lambda, but old lambda is still working.
Is there work arround
AWS a new policy AWSLambda_FullAccess. I created a role with AWSLambda_FullAccess and try to attach to lambda when deploy. but it did not work. (may be my method is wrong) every time it create a role
provider:
name: aws
stage: dev
region: us-east-1
iam:
role: arn:aws:iam::3373293854581:role/