Closed FugroEgger closed 2 months ago
Thanks for reporting this!
This issue should only occur when creating more than 5 schedules within a short amount of time, I have added it to our backlog to be fixed in an upcoming patch release.
Fixed in v3.0.1
Describe the bug Stack region: eu-west-1 Stack-Name: cs-instance-scheduler TagName: scheduler_period UsingAWSOrganizations: Yes regions: ap-southeast-1,ap-southeast-2,eu-central-1,eu-west-1,eu-west-3,eu-north-1,me-south-1,me-central-1,us-east-1,us-east-2,us-west-1 63 possible schedules
This ASGHandler (action: scheduler:run) in Hub account shows below error for multiple accounts/regions where ASG is not used (no groups configured). ASG scheduling works if ASG is tagged
Error message
To Reproduce
Expected behavior Number of values specified for the tag:scheduler_period should not be limited.
Please complete the following information about the solution:
[ ] Version: 3.0.0
[ ] Region: eu-west-1 (for hub and spoke stack deployment)
[ ] Was the solution modified from the version published on this repository? No
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[ ] Have you checked your service quotas for the sevices this solution uses? No
[ ] Were there any errors in the CloudWatch Logs? see above and attachment Troubleshooting
Screenshots none
Additional context All accounts are managed by Controltower, Minor SCP are active
ASGHandler_call.txt Cloudwatch_error.txt Cloudformation was used to create all schedules Iac_schedule_definition.template.txt