-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backup_window as parameter - feature request. #355
Comments
Hi @nalalia-1702 If I understand this correctly you are using maintenance windows for RDS instances? Can you provide documentation reference to the Backup windows? |
@nalalia-1702 was that the correct link? It goes to our documentation regarding maintenance window support but I think gockle was asking for more information on the backup windows you were requesting support for. |
hi @CrypticCabub @gockle, Backup Windows : Currently if I want the instance be started and stopped before and after Backup Window - I need to create additional period ( hardcode starting time and stopping time). Maintenance Windows: For MW currently you don't need to create additional period , right? you can just specify use_maintenance_window - true. ( for RDS). Would be really nice to have the same functionality for Backup Windows - we could just specify use_backup_window - true in a schedule , and Instance Scheduler could start and stop the instance automatically. for example: -schedule: Monday-Friday 8:00am-5:00pm for such case now we need to create additional period to have the instance started and stopped during BackupWindow. |
Hi team,
Currently to start and stop instance during maintenance window we don't need to add separated period, we just add parameter: use_maintenance_window - true.
Is it possible to implement the same functionality regarding "Backup windows" ?
It would get setting schedules much easier and more flexible. I think this is must have feature.
Thanks.
The text was updated successfully, but these errors were encountered: