Troubleshooting
This section provides troubleshooting instructions for deploying and using the solution.
Known issue resolution provides instructions to mitigate known errors. If these instructions don’t address your issue, Contact Support provides instructions for opening an Support case for this solution.
Known issue resolution
Problem: Instances not being scheduled in a remote account (v1.4-v3.0)
If you notice instances are not being scheduled in a remote account.
Resolution
Update the hub stack with the secondary account ID or complete the following task:
-
In the primary account, navigate to the CloudWatch console
-
In the navigation pane, select Logs > Log Groups.
-
Select the log group named
<STACK_NAME>-logs -
Search for the log stream for the Account ID (remote account).
-
For example, If there is no log stream named with the account ID, go to the DynamoDB console and select the table named
<STACK_NAME>-<ConfigTable>-<RANDOM>. -
Select Explore Items and select Run.
-
Select the item type Config.
-
Check if the attribute remote_account_ids has the account ID.
-
Check if the Account ID is not visible in this attribute.
-
If the solution is configured to aws organizations, then uninstall and reinstall the remote template in the remote account.
-
If the solution is configured to use remote Account IDs, update the cloudformation parameter Provide Organization Id OR List of Remote Account IDs with the list of account IDs where the instances are to be scheduled and where the remote template is deployed.
Problem: Instances not being scheduled (v3.1+)
If you notice instances are not being scheduled.
Resolution
-
Verify the resource has an IS-ManagedBy tag applied.
-
If the tag is not present, delete and recreate the Schedule tag to retrigger registration.
-
If the tag is still not being applied, verify the region is enabled for scheduling:
-
Check the hub/spoke stack configuration for the region, or
-
Navigate to the EventBridge console
in the same region as the resource and verify that the default event bus has event rules with the prefix IS-Tagging.
-
-
If the region is not enabled, update the Instance Scheduler stack to include the region in the regions CloudFormation parameter.
-
If the issue persists, review the solution administration logs for hub registration errors.
-
Confirm that your organization does not have policies in place that would prevent events from being forwarded from your account to the solution hub account.
Problem: Encrypted EC2 instances not starting
Instance Scheduler is reporting that EC2 instances with encrypted EBS volumes are being started, but they never actually start.
Resolution
Refer to Encrypted EC2 EBS Volumes for how to grant Instance Scheduler access to be able to schedule EC2 instances with encrypted EBS volumes
Problem: Unexpected API costs from informational tagging
Unexpectedly high costs from AWS Resource Groups Tagging API calls, AWS Config evaluations, or related remediation actions.
Resolution
Instance Scheduler writes informational tags to managed resources on each scheduling interval. If your environment enforces tag governance through AWS Config rules, tag policies, or automated remediation, ensure that Instance Scheduler’s tag keys are permitted. For the full list of tag keys and configuration guidance, refer to Tag governance considerations.
If you are unable to update your tag governance policies, disable
informational tagging by setting the Enable informational tagging
parameter to No on the hub stack.
Problem: RDS Instances not stopping when Create RDS Snapshots is Enabled
RDS Instances are not being stopped and the solution’s scheduler logs are reporting (AccessDenied) errors when calling the StopDBInstance operation due to not having rds:CreateDBSnapshot permission.
Resolution
Update the solution to v3.0.5 or newer or alternatively add the rds:CreateDBSnapshot permission to the solution’s scheduler role in each scheduled account.
