ShareSave by nOps
ShareSave Scheduler FAQs
This use case has been covered under the Scheduler tab. Here, users have the option to either stop or start a machine immediately based on the current status of the machine.
The Scheduler works through AWS Eventbridge. AWS Eventbridge is a lambda that runs based on a trigger event. Here the Scheduler is able to trigger the starting and stopping of the machine at a scheduled time.
nOps needs no additional writing access to the user’s environment. Instead, everything works through Eventbridge, keeping access limited and secure.
The recommendations we provide are filtered to exclude such machines. However, If you have also subscribed for Risk free ShareSave, then the machines covered under RI can be scheduled and the RI commitment can be adjusted for.
As the algorithm detects patterns of low utilization over a given period, the confidence level for a recommendation rises as the machine follows the recommended utilization pattern.
The ShareSave Scheduler is priced at the percentage of the cost saved by deploying the Scheduler. In Simple words, the customer pays only a small cut of the savings made through the tool.
Currently, the ShareSave Scheduler is able to provide recommendations for and schedule EC2 & RDS resources.
nOps will not charge the savings made through these manual starts and stops. Instead, nOps ShareSave has a dedicated page to understand the historical data of cost-optimized through nOps tools.
Ideally, no. Shutting down machines where RI coverage is applicable will not help you save significant money since you have already paid for the commitment. However, if you are already on-boarded for ShareSave Risk-Free Commitment, the machines can be scheduled because the flexibility of the ShareSave risk-free will help you acquire compounded savings.