- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
There are a few things you can check to troubleshoot why Instance Scheduler is not working for your RDS DB instance:
-
Make sure that the RDS DB instance is tagged with the correct schedule tag, The tag key must be
Schedule
and the tag value must be the name of the schedule that you want to apply to the instance. -
Check that the schedule is enabled. You can do this in the AWS Systems Manager console by navigating to Maintenance Windows and then selecting the schedule that you would like to check.
-
Make sure that the RDS DB instance is in a running state before the schedule is scheduled to start. If the instance is stopped, the Instance Scheduler will not be able to start it.
-
Check the CloudWatch logs for Instance Scheduler. You can find these logs in the CloudWatch console by navigating to logs and then selecting the Instance Scheduler log group.
If you have checked all of the above and Instance Scheduler is still not working for your RDS DB instance, you can try the following:
- Create a new schedule and tag the RDS DB instance with the new schedule tag.
- Restart the Instance Scheduler service. You can do this in the AWS Systems Manager console by navigating to Automation and then selecting the Instance Scheduler automation document.
- Open a support ticket with AWS.
If you are using the Instance Scheduler stack that is provided in the documentation, the following are some additional things to check:
- Make sure that the stack is deployed in the same region as the RDS DB instance.
- Make sure that the stack has the correct permissions to start and stop the RDS DB instance. You can check this by reviewing the stack's IAM role.
- Check the CloudFormation console for any errors with the stack.
If you are still having trouble getting Instance Scheduler to work for your RDS DB instance, please provide additional information about your setup, such as the version of Instance Scheduler that you are using, the region where your RDS DB instance is deployed, and the output of the CloudWatch logs for Instance Scheduler.
The following AWS documents are relevant to setting up and troubleshooting Instance Scheduler for RDS DB instances:
Troubleshooting - Instance Scheduler on AWS
These documents provide detailed instructions on how to deploy and configure the Instance Scheduler, as well as troubleshooting tips for common issues.
In addition, the following AWS blog post provides helpful information on setting up Instance Scheduler for RDS DB instances:
How to Schedule Amazon RDS Stop and Start using AWS Systems Manager
This blog post provides a step-by-step guide on how to use AWS Systems Manager to create and manage Instance Scheduler schedules for RDS DB instances.
If you are still having trouble getting the Instance Scheduler to work for your RDS DB instance, you can contact AWS Support for assistance.
- "Description": "(SO0030) instance-scheduler-on-aws v1.5.2", "AWSTemplateFormatVersion": "2010-09-09", "Metadata": { "AWS::CloudFormation::Interface": { "ParameterGroups": [ { "Label": { "default": "Scheduler (version v1.5.2)" }, "Parameters": [ "TagName", "ScheduledServices", "ScheduleRdsClusters", "CreateRdsSnapshot", "SchedulingActive", "DefaultTimezone", "ScheduleLambdaAccount", "SchedulerFrequency", "MemorySize" ]
- RDS is deployed At eu-west-1 region
- @message DEBUG : Can not schedule rds instance "umd-amusema-dev-db-stack-rrdsinstance-z0ikzxxxxxxu" because it is the source for read copy instance(s) umd-amusema-dev-db-stack-rrdsinstanceb-tpoyjg1zzuga @message DEBUG : Can not schedule rds instance "umd-amusema-dev-db-stack-rrdsinstanceb-tpoyjg1zzuga" because it is a read replica of instance umd-amusema-dev-db-stack-rrdsinstance-z0ikzxxxxxxu
- SchedulerPolicy "SchedulerPolicy": { "Type": "AWS::IAM::Policy", "Properties": { "PolicyDocument": { "Statement": [ { "Action": [ "rds:AddTagsToResource", "rds:RemoveTagsFromResource", "rds:DescribeDBSnapshots", "rds:StartDBInstance", "rds:StopDBInstance" ], "Effect": "Allow", "Resource": { "Fn::Sub": "arn:${AWS::Partition}:rds::${AWS::AccountId}:db:" }
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa