Guidelines for providing Instance Scheduler to Modernisation Platform customers

[dms1981]

User Story

As a modernisation platform team member I want to define guidelines for using Instance Scheduler So that we offer a consistent experience to customers that balances cost-efficiency with user needs.

Value

This story should cover the discussion of topics related to incorporating the AWS Instance Scheduler with the Modernisation Platform. This story may require some user research.

Questions / Assumptions

• Assumption: We will use an "opt-out" approach to scheduling instances.
• Assumption: We will include EC2 and RDS instances in scheduling scope.
• Assumption: Schedules will be defined by the Modernisation Platform team in the code that calls the Instance Scheduler module
• Assumption: A default schedule operating during weekdays will run between 06:50 and 19:00
• Question: How will new accounts be added to the table of accounts in scope? (eg, how will values be added to the dynamoDB entry for cross_account_roles? How will customers define their scheduling requirements?)
• Question: What will default times look like?
• Question: How will tags be added to instances? (eg, how will we ensure that a user-created resource such as an EC2 instance gets tagged with auto-scheduler=default)
• Question: Will production resources be excluded from scheduling? If so, how?

Definition of done

• [ ] full discussion has taken place
• [ ] any required user research has taken place
• [ ] Architectural Decision Record has been updated
• [ ] subordinate stories have been created as required

Reference

How to write good user stories Recreate AWS Instance Scheduler in Terraform

[dms1981]

Moved to blocked as this is dependent on #1844

[gfou-al]

https://github.com/ministryofjustice/modernisation-platform/pull/2529