Project Defaults

Project Defaults

Project Defaults configure the baseline settings for your SkySaver project. These settings apply to all connected AWS accounts unless overridden at the account level.

Accessing Project Defaults

Navigate to Tenant Management and click the Defaults tab.

Project Defaults Project Defaults

Available Settings

SettingDescriptionDefault
Project NameDisplay name for your SkySaver project
Default Automation TagTag key for schedule matching on AWS resourcesSkySaverSchedule
Default Cross-Account RoleIAM role name SkySaver assumes in your accountsSkySaverScheduler
Default External IDSecurity token for role assumptionAuto-generated
Default RegionsAWS regions to scanNone (must configure)
Default Enabled CapabilitiesWhich resource types to schedule (EC2, RDS, ASG, ECS, Lambda)None
Cost Allocation TagsToggle to process all discovered cost allocation tagsOff

Configuring Services

Enable the AWS services you want SkySaver to manage:

Available Services

ServiceDescription
EC2Elastic Compute Cloud instances
RDSRelational Database Service instances
LambdaLambda functions (concurrency)
ASGAuto Scaling Groups
ECSElastic Container Service

Enabling Services

  1. Navigate to Tenant Management > Defaults tab
  2. Check the boxes for desired capabilities under Default Enabled Capabilities
  3. Click Save All Settings

Note: Only enabled services will be scanned for scheduling. Enable only what you need to minimize API calls.

Configuring Regions

Add all AWS regions where your resources are located:

Adding Regions

  1. Navigate to Tenant Management > Defaults tab
  2. Type a region name in the Default Regions field (e.g., us-east-1)
  3. Click Add
  4. Click Save All Settings

Common Regions

RegionDescription
us-east-1N. Virginia
us-west-2Oregon
eu-west-1Ireland
eu-central-1Frankfurt
ap-southeast-1Singapore

Tag Configuration

The Default Automation Tag is the AWS resource tag key used for schedule matching:

Setting the Default Automation Tag

  1. Navigate to Tenant Management > Defaults tab
  2. Find the Default Automation Tag field
  3. Enter your preferred tag key (e.g., SkySaverSchedule)
  4. Click Save All Settings

Tag Considerations

  • Keep tag names consistent across accounts
  • Avoid spaces in tag names
  • Consider including “SkySaver” for clarity
  • Document your tag naming convention

Role Configuration

Default Cross-Account Role

The IAM role name that SkySaver assumes in your AWS accounts:

  • Default: SkySaverScheduler
  • Must match the role created by CloudFormation
  • Can be overridden per account

External ID

A security token used when assuming IAM roles:

  • Auto-generated UUID per project
  • Must match the External ID in your IAM role trust policy
  • Keep this value secure

Saving Settings

To save project defaults:

  1. Make your changes in the form
  2. Click Save All Settings
  3. Changes take effect immediately

Account-Level Overrides

Individual AWS accounts can override these defaults:

SettingOverride Location
TagTenant Management > Accounts tab > Edit
RegionsTenant Management > Accounts tab > Edit
ServicesNot overridable (project-wide)

Cost Allocation Tags Configuration

Configure which AWS cost allocation tags SkySaver uses for the Cost By Tag dashboard chart and Cost Explorer tag filters.

Prerequisites

Tags must be activated in your AWS Billing Console before adding them here. See Cost Allocation Tags for AWS activation steps.

Enabling Cost Allocation Tags

  1. Navigate to Tenant Management > Defaults tab
  2. Scroll to the Cost Allocation Tags section
  3. Toggle Process All Tags on to automatically include all discovered tags in cost breakdowns
  4. Click Save All Settings

Tip: When Process All Tags is enabled, all cost allocation tags active in your AWS Billing Console will appear in Cost Explorer filters and the Cost By Tag chart.

Best Practices

  1. Start minimal - Enable only necessary services
  2. Be consistent - Use the same tag across all accounts
  3. Document - Record your External ID securely
  4. Review regularly - Audit settings as needs change

Impact of Changes

ChangeEffect
Enable serviceStarts scanning that resource type
Disable serviceStops all scheduling for that type
Add regionStarts scanning in new region
Remove regionStops scanning in that region
Change tagMust update AWS resource tags to match

Troubleshooting

IssueCauseSolution
Resources not foundRegion not addedAdd region to defaults
Schedules not runningService not enabledEnable service in defaults
Role assumption failsExternal ID mismatchVerify External ID matches