Closed gfou-al closed 2 years ago
The kms:CreateGrant permission when applied to instance scheduler role in member accounts resolved the issue. We're considering to add some filtering to restrict the permission.
https://github.com/ministryofjustice/modernisation-platform/pull/2559 <-- restricting kms:CreateGrant
permission
When invoking the Instance Scheduler lambda manually through the AWS web console in core-shared-services account.
The
sprinkler-db-mgmt-server
is stopped through the lambda, but cannot be started. The lambda logs are not reporting any error because the message to start the instance is successful. However, the EC2 reports the following errors after some time:This behaviour only seems to apply to
sprinkler-db-mgmt-server
whereas a temporal instance I created did not have the same issue.The following PR unfortunately did not resolve the issue and might have to be reverted:
Add "kms:CreateGrant" to instance scheduler role to try fixing the issue