Cloud service providers follow a pay-as-you-go pricing model, meaning organizations incur charges only when their machines are running. Unfortunately, there are often instances where servers run continuously, even when they don't need to operate around the clock or during weekends. This results in increased cloud costs. The solution to this predicament lies in implementing AI-driven policy scheduling. The key objective is to identify when instances should start or stop running, and schedule periods of inactivity for your resources to reduce cloud expenses.
ProfiseaLabs experts have developed Cloudsitter, the intelligent scheduling feature. With this innovative functionality, you can activate AI-powered scheduling, establish the most optimal hibernation policy, and ensure you don't pay for idle resources.
When you access the Cloudsitter dashboard, you'll find a comprehensive list of all your resources that can either be active or in hibernation.
For additional recommendations, click on the ‘Suggestions’ tab. This chart displays the types of resources we work with, including EC2, Databases, EKS, ECS, ASG, and SageMaker.
You also can manage Kubernetes resources in the ‘K8s suggestions’ tab. More information on this is available in this article.
General
Consequently, you can track which resources are currently active and which are in hibernation. Furthermore, you can view the estimated savings suggested by Uniskai for each of your resource items.
Use the slider to manually switch the state of your resources.
To view an instance of one of the interactive diagrams in the Cloudview, click on the three dots.
To sort the resources, click on the header of each column.
For immediate AI scheduling recommendations, click on ‘View Suggestions’.
Once you click ‘View Suggestions’, you'll see a display similar to the example below. It provides information on when your resource is active and not in use. Our system performed the analysis over two weeks to generate this suggestion. As a result, if you follow the same schedule, you can save approximately $10.07 per month, as shown in the example below. This allows you to automatically schedule hibernation for your resources and follow intelligent suggestions by Uniskai.
View the usage history of resources from the previous week by clicking on the icon.
Red indicates times when the resource was in hibernation, while green indicates when it was active.
To create a schedule to automatically start/stop your resources, go to the “Policies” tab and click “New Policy.”
In this new policy, you need to provide a name, attach the necessary resources, and select the time period for your policy. After filling in all the required details, click “Save”.
Granularity
You can choose the granularity of the policy based on your requirements, whether it's hourly or every 15 minutes. To activate it, toggle the switch. Green fields indicate the instance is running, while red fields signify it's in hibernation.
Notifications
To receive email notifications, you can enable the ‘Email notifications’ slider. By default, the field displays the email address that you specified during registration on the site.
You'll receive an email notification in case the policy fails to turn your resources on or off for any reason. You can also add another email address or turn off notifications.
The ‘Policies’ tab displays your list of policies, as well as team policies.
Information about the total savings amount, current month's savings, and resource details are presented to the right of the policies.
In the ‘Scheduled’ tab, you can see all the resources included in the policies. To add a resource to this table, select the resource and click on ‘Assign’. You can either add this resource to an existing policy or create a new one.
There are also quick policy actions available within the ‘Scheduled’ tab:
Shutdown: Stops the resource, putting it in hibernation.
Wake up: Starts the resource, putting it in an active state.
Assign policy: Links the policy to a specific resource.
Detach policy: Disables the policy for a specific resource.
Suspend policy: Pauses the policy for a specific resource. The resource can be in any state while paused, and when the pause ends, the policy will return the resource to its original state according to its schedule.
Set delay: Allows you to delay the start and end of the start/stop policy for a certain specified time
You can also assign the policy or take action on several resources. To do this, select the resources and choose the action.
AI-powered Cloudsitter analyses user behaviour patterns and offers unique smart scheduling recommendations, helping you save on your cloud budget. With a user-friendly interface, you can effortlessly manage your resources and start or stop them directly from the dashboard, even without specialized expertise. This feature is invaluable to both DevOps engineers and managers, as it collects valuable information and can lead to savings of up to 60% on cloud costs.
You can filter resources by selecting the desired filter in the dropdown and clicking the ‘Apply’ button. Verify that the data is displayed per the selected filters.
Additionally, you can search for specific data by entering the necessary information in the corresponding field and ensuring that the data is displayed correctly.
You also have the option to create a new policy during the assignment of a policy. Click the ‘Assign’ button and then click ‘Create new policy.’
Add all the required settings and click the ‘Save’ button.
Your resource will be automatically added to the new policy.
K8s tools
To utilize the comprehensive monitoring capabilities, optimal performance, and resource allocation within your EKS namespaces, make sure the cluster is connected via the API.
Policy delay
Policy Delay allows you more flexibility in managing your policies. We'll show you how to use it.
First, click on the Actions button and then select Set a delay.
After that, enter a value in the corresponding box (you cannot set more than half of the time interval change).
If you set a delay of 10 minutes, here's how it will work:
If a delay is set and resources are to be started, they will be started later with the set delay, if a resource is to be stopped, it will be stopped earlier by a time equal to the delay.
For example, your resources have a sleep state and are scheduled to wake up at 10:00, if you set a delay of 10 minutes, it will work like this: your resources will be started at about 10:10. Let's imagine that the change of policy status from run to sleep is scheduled for an hour later, i.e. at 11:00, if you use the delay, the resources will be stopped at 10:50.
Save the changes and enjoy. .
