KMSAccessDeniedException error occurs when an IAM role is deleted, then another role created with the same name. IAM roles have an internal ID, and the Lambda function is now referring to a deleted IAM role.
- go to AWS console
- go to AWS lambda services and search for
- go to Configuration tab
- change Execution role
StackStateTopoCronRoleto any other role you currently have (if you don’t have any other role, create a temporary one by selection the option Create a new role from AWS policy templates)
- change Execution role back to
- save again
- go to Test tab and execute the
stackstate-topo-cronLambda by pressing test button (use
hello-worldsample for creating test event)
Article is closed for comments.