KMS CMKs and AWS Accounts on scheduler 1.5.6 version

[rootops]

Hello,

We are using AWS Instance Scheduler to manage the start and stop operations of EC2 and RDS instances across a large-scale deployment . Each account has different KMS Customer Managed Keys (CMKs) for encryption ( actually start instances not working), and we need to ensure that the Instance Scheduler can handle this complexity efficiently.
i need clarification on How does it manage the start and stop operations when different KMS CMKs are used across accounts?

NB: my actual version is 1.5.6

Regards,
M.B

[CrypticCabub]

starting with version 3.0.0, Instance Scheduler provides a place in the cloud formation templates for you to specify your KMS keys to provide the scheduler limited access for the purpose of starting encrypted EC2 instances. You can find documentation of this feature here: https://docs.aws.amazon.com/solutions/latest/instance-scheduler-on-aws/security-1.html#encrypted-ec2-ebs-volumes

for 1.5.x, this can still be achieved, but you would need to manually apply the permissions to your solution's scheduling role in each spoke account.