Skip to content

Landing Zone Autopilot

The landing zone runs itself, at two layers: the estate follows your organization, and resources follow schedules, budgets and triggers.

Overview

RosettaHub automates recurring cloud operations so that governance and cost control don't depend on manual intervention. Automation capabilities span the full resource lifecycle -- from scheduled start/stop to budget-triggered shutdowns and compliance-driven remediation.

Autopilot operates at two layers, and they compose:

Layer What follows automatically Covered in
The estate Which accounts exist, who reaches them, under what budget and permissions. Someone joins and their account, budget and roles follow; someone leaves and access is revoked everywhere The Landing Zone
The resources What happens to machines and storage inside those accounts: schedules, idle timeouts, budget triggers, remediation This page

The estate layer decides an account exists with a budget. This layer decides what happens to the machines inside it when that budget runs low.

Capabilities on this layer

Capability Description
Scheduled tasks Cron and rate-based tasks to start, stop, reboot, or terminate resources on a schedule
Auto-stop idle instances Automatically stop instances that have been idle beyond a configurable timeout
Budget-triggered actions Automatically disable cloud accounts or stop resources when budget ceilings are reached
Compliance remediation Cloud Custodian policies automatically tag, stop, or modify non-compliant resources
Spot instance handling Automatic snapshot, hibernation, or replacement when spot instances are reclaimed
Account lifecycle Automated account vending, key rotation, and abuse response

Scheduling

RosettaHub provides built-in task scheduling for automating recurring operations on cloud resources. Tasks run against cloud accounts and can target any resource within the account.

Task Types

Type Description Example
Rate Tasks Execute at a fixed interval Every 6 hours, every 30 minutes
Cron Tasks Execute on a cron schedule Weekdays at 6 PM, first Monday of each month

Common Use Cases

Use Case Task Type Description
Auto-stop idle machines Cron Stop running instances outside business hours (e.g., 7 PM weekdays)
Scheduled cleanup Rate / Cron Remove temporary resources on a schedule
Budget checks Rate Periodic cost threshold monitoring
Backup snapshots Cron Create regular snapshots of block storage (e.g., nightly)
Start lab environments Cron Pre-launch workshop formations before a scheduled class
Compliance scans Rate Run Cloud Custodian policies at regular intervals

Creating Tasks

Rate and Cron tasks are created from the cloud account context menu:

  1. Navigate to the Cloud Accounts view
  2. Right-click a cloud account
  3. Select Create Rate Task or Create Cron Task
  4. Configure the schedule and target action
  5. The task appears in the Calendar view

Calendar View

The Calendar view provides a visual overview of all scheduled tasks across your cloud accounts. Tasks are displayed on a timeline so you can see what runs when and identify scheduling conflicts.

Managing Tasks

View Description
Calendar Visual calendar showing all scheduled tasks
Rate Tasks List and manage all rate-based tasks
Cron Tasks List and manage all cron-based tasks

Tasks can be paused, modified, or deleted from their respective views.