Resource Scheduling

Resource Scheduling

Resource Scheduling is SkySaver’s core feature for automating AWS resource management. Create schedules to automatically start, stop, and scale resources based on time patterns.

Overview

Schedules define:

  • What resource types to manage (EC2, RDS, Lambda, ASG)
  • When resources should be active or inactive (periods)
  • How resources should be configured during each state

Supported Resources

ResourceActionsUse Cases
EC2Start/Stop, Instance TypeDev environments, batch processing
RDSStart/Stop, Instance ClassNon-production databases
LambdaConcurrency scalingCost control, burst management
ASGCapacity scalingVariable workloads

How Scheduling Works

graph LR
    A[Create Schedule] --> B[Add Periods]
    B --> C[Tag Resources]
    C --> D[Scheduler Runs]
    D --> E[Resources Managed]
  1. Create a schedule - Define name, type, and timezone
  2. Add periods - Specify when resources should be active
  3. Tag resources - Apply schedule tag to AWS resources
  4. Scheduler runs - SkySaver continuously monitors and acts
  5. Resources managed - Resources start/stop per schedule

Active vs Inactive

StateTimingResource Behavior
ActiveWithin a periodRunning, scaled up
InactiveOutside all periodsStopped, scaled down

Example: Business Hours Schedule

A schedule for development EC2 instances running Monday-Friday, 9 AM - 6 PM:

Schedule: dev-business-hours
Type: EC2
Timezone: America/New_York

Period 1:
  Start: 09:00
  End: 18:00
  Days: Mon, Tue, Wed, Thu, Fri

Result: Instances start at 9 AM, stop at 6 PM on weekdays.

In This Section

PageDescription
Creating SchedulesStep-by-step schedule creation
Schedule TypesResource-specific configuration
PeriodsConfiguring time windows
Managing SchedulesEdit, delete, and monitor
ExamplesCommon scheduling patterns
Tagging ResourcesHow to tag AWS resources

Quick Start

  1. Navigate to Schedules > Add Schedule
  2. Enter a schedule name (e.g., dev-business-hours)
  3. Select resource type (e.g., EC2)
  4. Choose timezone
  5. Add a period with start/end times
  6. Save the schedule
  7. Tag your AWS resources with the schedule name

Prerequisites

Before creating schedules:

  1. Connect AWS accounts - Add accounts to your project
  2. Enable services - Toggle services in Project Defaults
  3. Deploy IAM role - Complete AWS Account Setup

Best Practices

  1. Use descriptive names - Include resource type and timing (e.g., ec2-dev-business-hours)
  2. Consider timezones - Use consistent timezones across schedules
  3. Start conservatively - Test with non-critical resources first
  4. Document schedules - Maintain a schedule inventory
  5. Review regularly - Audit schedules as needs change