AWS (legacy) StackPack - KMSAccessDeniedException when reinstaling AWS Cloudformation stacks

The 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.

Fix procedure:​

1. go to AWS console
2. go to AWS lambda services and search for stackstate-topo-cron function
3. go to Configuration tab
4. change Execution role StackStateTopoCronRole to 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)
5. save
6. change Execution role back to StackStateTopoCronRole
7. save again
8. go to Test tab and execute the stackstate-topo-cron Lambda by pressing test button (use hello-world sample for creating test event)