DynamoDB not updating following CloudFormation Update about instance-scheduler-on-aws HOT 5 CLOSED

Hi Neil,

How did you extend the CrossAccountRoles parameter? The limitation you described is a known limitation for which Instance Scheduler provides 2 alternative solutions for out of the box

The first option is to use automatic spoke account registration via AWS Organizations.

The second option would be to define your spoke account IDs using SSM parameters and let the solution dynamically load these account ids directly from SSM during scheduling.

You can find details on both of these approaches in our IG here:
https://docs.aws.amazon.com/solutions/latest/instance-scheduler-on-aws/cross-account-instance-scheduling.html

I hope that helps!
Cryptic

from instance-scheduler-on-aws.

Hi Cryptic,

Thank you for reaching back. The following is what I wrote up following my interaction with Support. It seemed to work but maybe is not a viable solution? I have attached my notes as an attachment. Hope that has come through.

Many thanks.

from instance-scheduler-on-aws.

You can use that method if you would like to manually edit the cloud formation template. However what Support could not have known is that Instance Scheduler already provides a built-in way to handle this scenario without needing to modify the template (quite helpful when updating to new versions).

If you are on the latest version (1.5.1), the preferred approach would be to use automatic registration with AWS Organizations. If that doesn't work for you, I would recommend using the SSM Parameters approach as it will allow you to add additional accounts to the ssm parameter without having to issue an extra CloudFormation update

from instance-scheduler-on-aws.

Hi Cryptic,

So I have upgraded our hub and spoke to 1.5.1. I have elected to use the account ID in the parameter and all appears to be working :). Is there a way to calculate the quota used in the actual parameter field. We have over 300 accounts and we have not long started pushing this out. I don't think we would hit the same issue (4096) but it would be handy to be able to monitor this. Thank you for your support and pointers with this. I am going to close the case.

from instance-scheduler-on-aws.

in terms of the number of characters being used in the CloudFormation? I am not aware of a convenient way of monitoring that specifically, but I will note that the SSM Parameter support provided by Instance Scheduler allows you to define multiple accounts per SSM parameter (as a comma-separated list) and you can then provide multiple SSM parameters to the CloudFormation input field. Together this means that the theoretical upper limit should be far beyond real-world use cases

from instance-scheduler-on-aws.