Troubleshooting
Troubleshooting
This section helps you diagnose and resolve common issues with SkySaver.
Quick Diagnostics
Before diving into specific issues, check these common causes:
| Symptom | First Check |
|---|---|
| Resources not scheduling | Is the service enabled in Project Defaults? |
| Account shows unconfigured | Is the IAM role deployed? |
| No cost data | Is Cost Explorer enabled in AWS? |
| Automation failed | Check IAM permissions in Automation Reports |
| Can’t see features | Verify RBAC permissions for your user |
In This Section
| Page | Description |
|---|---|
| Common Issues | Frequently encountered problems and solutions |
| IAM Permissions | Resolving AWS permission errors |
| FAQ | Frequently asked questions |
Getting Help
If you can’t resolve your issue:
- Check the relevant documentation section
- Review error messages in Automation Reports
- Verify AWS CloudTrail for API errors
- Contact SkySaver support through the portal
Diagnostic Checklist
Use this checklist to systematically diagnose issues:
Account Configuration
- AWS account added to project
- IAM role deployed via CloudFormation
- External ID matches between SkySaver and IAM role
- Account shows as “Configured” in Accounts > Manage
Project Setup
- Desired services enabled (EC2, RDS, Lambda, ASG)
- Correct regions added
- Default tag is set
- User has appropriate RBAC permissions
Scheduling
- Schedule created with correct type
- Periods configured with valid times
- AWS resources tagged with schedule name
- Tag key matches project/account configuration
Cost Explorer
- AWS Cost Explorer activated in AWS account
- IAM role has Cost Explorer permissions
- Wait 24-48 hours for initial data
Automations
- Automation is enabled (for Continuous/Cadence types)
- IAM role has required permissions
- Check Automation Reports for error details
Common Error Messages
| Error | Meaning | Solution |
|---|---|---|
| “Access Denied” | IAM permission missing | Review IAM Permissions |
| “Role not found” | IAM role doesn’t exist | Deploy CloudFormation template |
| “External ID mismatch” | Security token incorrect | Verify External ID in Project Defaults |
| “Resource not found” | Resource was deleted | Update or remove schedule |
| “Throttling” | AWS rate limit | Reduce scan frequency |
Logs and Reports
Automation Reports
View detailed execution logs:
- Navigate to Automation Reports
- Find the failed execution
- Click to view details
- Review error messages
AWS CloudTrail
For deeper investigation:
- Open AWS CloudTrail in AWS Console
- Filter by session name prefix:
SkySaver-*to see all SkySaver activity - Look for
AccessDeniedevents - Review the specific API call that failed
Tip: SkySaver uses session names with the
SkySaver-prefix followed by the automation type:
SkySaver-scheduler-{uuid}- Resource scheduling operationsSkySaver-coh-{account-id}- Cost Optimization Hub processingSkySaver-opportunities-{account-id}- Opportunities generation
Health Checks
Periodically verify SkySaver is working correctly:
- Account status - All accounts show “Configured”
- Recent activity - Dashboard shows recent executions
- Schedule execution - Resources are starting/stopping as expected
- Cost data - Cost Explorer shows current data