This week, we are excited to announce our new "RI Utilization" feature at nOps. This feature is designed to provide our clients with a historic utilization view of their Reserved Instances (RI) by collecting their monthly RI usage data and storing it in a database. It enables AWS users to track, manage, and optimize their RI usage, ensuring that they are making the most of their investment. Collecting monthly RI usage data and storing it in a centralized database makes it easier than ever for clients to track and analyze their RI utilization

With this new feature, users can effortlessly access their RI utilization data and gain valuable insights into how effectively they're using their RIs. This enables customers to identify underutilized RIs and take action to reduce waste, such as modifying or selling unused RIs. Armed with this information, they can make informed decisions and take action to optimize their RI utilization, ultimately leading to cost savings and increased efficiency. By leveraging this powerful feature, AWS users can significantly reduce their cloud infrastructure costs while still maintaining the performance and availability of their workloads.

To manage your own RI Utilization recommendations in nOps, see Commitment Management Solutions

At nOps, our top priority is to ensure that our clients have access to the most effective tools and features available to manage their AWS infrastructure. With this goal in mind, we are proud to introduce the RI Utilization feature as an essential addition to our platform. This feature empowers our clients to maximize their AWS investment by optimizing Reserved Instance (RI) utilization and reducing unnecessary expenses. 

We strongly believe that this feature will enable our clients to achieve their cost optimization objectives more efficiently, providing them with greater financial flexibility and business agility. At nOps, we are committed to continuing to develop innovative solutions that meet the evolving needs of our clients and help them succeed in the cloud.

To learn more about nOps Reserved Instances Utilization, see website.

This week nOps launched an efficient way how you can schedule your idle EKS clusters idle time with nSwitch
If you're looking for a simple yet effective way to optimize your cloud infrastructure costs, nSwitch's workload-based scheduling feature could be just what you need. And now, nOps nSwitch has taken this functionality to the next level by introducing support for scheduling EKS cluster node groups to be scaled down during off-hours. This means you can now easily schedule your EKS cluster node groups to be powered down during non-essential hours, reducing your cloud infrastructure costs and optimizing your resources. By eliminating the need for manual scaling

nOps has made significant updates to its EKS cluster management tools, including new workload-based recommendations and the ability to create schedules for powering down idle clusters during off-peak hours.

To see your own EKS Cluster Scheduler recommendations in nOps, see Scheduler Recommendations

These new features are part of nOps ongoing efforts to help customers optimize their cloud infrastructure and reduce costs. By incorporating workload-based recommendations, nOps aims to simplify the process of optimizing EKS clusters by providing tailored recommendations based on real-time usage data.

Additionally, the ability to create schedules for powering down idle clusters during non-essential hours is a game-changer for companies looking to save on cloud infrastructure costs without sacrificing performance. Let's take a closer look at these new features and what they mean for EKS cluster management.

nSwitch's EKS schedules are perfect for a variety of workloads, including Dev and QA infrastructure, batch processing, and time-zone-specific workloads. By leveraging nSwitch's EKS schedules, you can maximize the efficiency and cost-effectiveness of your EKS clusters, without sacrificing performance or reliability. With customers reporting savings of up to 70% on EC2, RDS, and EKS spend, nSwitch has proven to be an effective cost-optimization tool

To learn more about nOps nSwtich EKS Cluster savings recommendations, see website.

Starting this week, nOps launched Business Contexts. With the improved cost allocation tool you can allocate every single dollar of AWS spend by handling untagged and miss-tagged resources.

Business Contexts gives users the unparalleled ability to access and allocate every dollar of their cloud spend in real-time. It continuously distributes AWS costs, handles tag misconfiguration, and spreads shared costs to multiple teams and business units. With multiple teams responsible for provisioning resources, it's common to encounter discrepancies in their approaches towards tagging. Additionally, certain costs, such as bandwidth and AWS business support expenses, are shared. 

• Does your organisation battle with teams taking ownership of their cloud bill?
• Do you need help keeping track of expenses and staying within your Cloud budget?

Well, no more! nOps helps you to allocate every dollar of your AWS bill. nOps ML continuously allocates AWS costs, handles tag misconfiguration, and spreads shared costs to multiple teams and business units. Build a culture of accountability by adding your business context to every dollar of AWS spend. Easily create dynamic allocation rules by region, tags, operation, accounts, and usage types. We allow users to access years worth of cloud billing data in an interactive environment, which could easily amount to millions or billions of rows of data across thousands of billing dimensions.

With nOps, you can efficiently allocate your cloud costs across suitable business units and business outcomes. Efficiently distribute shared costs like bandwidth or support across the right teams. These shared costs are distributed among teams based on fixed percentages or average weights. Handle untagged and miss-tagged resources to allocate every single dollar of AWS spend.

Try nOps Business Contexts today! 

This week nOps Scheduler page has been loaded with lots of new UI and feature enhancements. The latest version now contains a Schedule Grid that gives you the ability to quickly identify and schedule a group of resources with just one click right away from the schedule grid. It offers an easy to use UI which helps you achieve your scheduler needs right away without spending too much time exploring and setting up the schedules individually.

To see and explore this Recommended Schedules in nOps, see nOps Scheduler . 

This week, nOps launched grouped recommendations by EC2 resources. With this new feature, nOps provides multiple EC2 recommendations for a single EC2 resource as a group which comes directly from smart nOps AI engine. These robust recommendations help you see the maximum savings opportunities that can be availed with just a few clicks by setting up the desired schedule from the list of recommendations.  

The EC2 recommendations are a part of the nOps ShareSave program, and you can find the EC2 recommendations in the List of Opportunities section. Each EC2 recommendation consists of an Opportunity Name, Instance Type , Account Name, Region, Schedule (Not Scheduled or Scheduled), Total Savings, and an Action to schedule the recommendation.

To see your own EC2 Recommendations in nOps, see EC2 Recommendations.

This week, nOps launched RDS Cluster Scheduling. With this new feature, you can now schedule entire RDS clusters in just a few clicks. You can find the RDS clusters to schedule in the Create Schedule modal on the Scheduler page. In the last version, RDS recommendations only provided RDS instances recommendations.

The RDS recommendations are a part of the nOps ShareSave program, and you can find the RDS recommendation in the List of Opportunities section. Each RDS recommendation consists of an Opportunity Name, RDS Type (Single Instance and Cluster), Instance Size, Account Name, Region, Schedule (Not Scheduled or Scheduled), New Config (Recommended Configuration), Total Savings, and an Action to schedule the recommendation.

You can also click on the opportunity name to see the details of the usage and the recommendation in the form of line charts. To schedule a recommendation, simply click on the Schedule button, give your schedule a name and click create, all other fields are populated automatically.

To see your own RDS Recommendations in nOps, see RDS Recommendations. 

nOps RDS Scheduler now provides Metadata of Database Instances

nOps RDS Scheduler now provides nOps users the ability to see the metadata of the RDS database instances in the recommendations. To see the metadata of database instances, go to ShareSave > List of Opportunities > Amazon Relational Database Service > RDS Scheduler > [Database Instance] and click on any recommendation to see the metadata.

Alongside metadata, you can also see the details of the database connections, CPU utilization, and the recommendation in the form of line charts with Database Connections on the y-axis and the time of day on the x-axis. 

The RDS recommendations are a part of the nOps ShareSave program, and you can find the RDS recommendation in the List of Opportunities section on the ShareSave page.

To see your own RDS Recommendations in nOps, see RDS Recommendations.

nOps Scheduler for RDS Scheduling now Groups Recommendations by Database Instances

nOps RDS Scheduler now groups recommendations by database instances to allow greater visibility and control over the recommendation. nOps can offer multiple recommendations for the same instance or cluster, and you have the ability to choose which recommendation to implement. The grouping of recommendations based on database instances will allow you to quickly grasp the difference in recommendations and choose the best recommendation according to your requirements. 

The RDS recommendations are a part of the nOps ShareSave program, and you can find the RDS recommendation in the List of Opportunities section. Each RDS recommendation consists of an Opportunity Name, RDS Type (Single Instance and Cluster), Instance Size, Account Name, Region, Schedule (Not Scheduled or Scheduled), New Config (Recommended Configuration), Total Savings, and an Action to schedule the recommendation.

To see your own RDS Recommendations in nOps, see RDS Recommendations.

This week nOps launched a feedback model in nOps Resource Scheduler recommendations. With this new feature, you can mark Resource Scheduler recommendations as appropriate to implement or not.

The feedback will help you: point out recommendations that you want your team to implement right away, or block out recommendations that you feel are not ready to be implemented for any reason. Your feedback will also help nOps AI to improve the recommendations further.

To see your own Resource Scheduler recommendations in nOps, see Resource Scheduler Recommendations. To learn more about Resource Scheduler recommendations, visit the website.

nOps Announces ShareSave RDS Recommendations

nOps ShareSave now provides customers with RDS recommendations. The RDS recommendations clearly describe the optimization approach you should take and shows the recommendations to implement.

The RDS recommendations are a part of the nOps ShareSave program, and you can find the RDS recommendation in the List of Opportunities section. Each RDS recommendation consists of an Opportunity Name, RDS Type (Single Instance and Cluster), Instance Size, Account Name, Region, Schedule (Not Scheduled or Scheduled), New Config (Recommended Configuration), Total Savings, and an Action to schedule the recommendation.

You can also click on the opportunity name to see the details of the usage and the recommendation in the form of line charts. To schedule a recommendation, simply click on the Schedule button, give your schedule a name and click create.

To see your own RDS Recommendations in nOps, see RDS Recommendations. 

Starting this week, nOps ShareSave Auto Scaling Group recommendations now also provide you the metadata of the Auto Scaling Group along with the recommendations. The metadata for each Auto Scaling Group includes the name, instances, region, maximum amount of instances, the minimum amount of instances, the desired capacity of instances, group creation date, and the associated tags.

nOps Auto Scaling Group Recommendations allow you to determine your group's idle resources using statistical analysis based on the group’s utilization data. It also allows you to automatically reconfigure your autoscaling group based on actual usage. With nOps Auto Scaling Group recommendation you also get the most optimal personalized configuration based on the historical utilization data that allows you to keep only the amount of resources you need running.

To learn more about nOps Auto Scaling Group Recommendations, visit the website.

nOps ShareSave Auto Scaling Groups Introduces Hot Recommendations

This week, nOps launched the Hot Recommendations feature in ShareSave Auto Scaling Groups recommendations. These recommendations are some of the most lucrative cost-cutting opportunities for nOps customers.

The addition of this new feature does not affect the functionality of the nOps ShareSave AutoScaling Groups Recommendations, it simply adds more variety to the existing recommendations and allows you to schedule resources with more confidence.

To learn more about nOps Auto Scaling Group Recommendations, visit the website.

nOps Scheduler now supports the scheduling of KMS Encrypted EBS Volumes with the help of EventBridge. To schedule KMS Encrypted resources with the nOps scheduler, all you need to do is to connect the KMS ARN with the EventBridge and nOps Scheduler will take care of the rest.

Trying to schedule encrypted resources without connecting a KMS ARN with the EventBridge can result in undesired effects.

To connect the KMS ARN with the EventBridge, Go to the nOps > Organization Settings > Integrations > EventBridge and click Add Key in KMS Stack. You will be redirected to the CloudFormation Stack creation page of your AWS console. Provide your KMS ARN and click Create Stack.

To learn more, see documentation.

nOps Unveils New Visualization for Auto Scaling Groups Recommendations in ShareSave

You can see One Time Configuration and Dynamic Configuration recommendations separately in Auto Scaling Group Recommendations. With this new visualization, you can easily keep track of the type of recommendations and your selected configurations. The new visualization also offers you the ability to see the number of schedules implemented on a resource. 

Each recommendation that you see in one configuration section will have an equivalent recommendation in the other configuration section, the only difference will be the configuration.

To learn more about nOps Auto Scaling Groups recommendations, see website.

nOps Now Provides a Feedback Model in Auto Scaling Groups Recommendation

This week nOps launched a feedback model in nOps Auto Scaling Groups recommendation. With this new feature, you can mark Auto Scaling Groups recommendation as appropriate to implement or not quite right.

The feedback will help you: point out recommendations that you want your team to implement right away, or block out recommendations that you feel are not ready to be implemented for any reason. Your feedback will also help nOps AI to further improve the recommendation.

To learn more about nOps Auto Scaling Groups recommendations, see website.

You can now use nOps Scheduler to hibernate EC2 instances and then bring them back to life when you need them. The hibernation process stores the in-memory state of the instance, along with its private and elastic IP addresses, allowing it to pick up exactly where it left off. While creating a schedule, simply toggle the Hibernate option and nOps Scheduler will hibernate the scheduled resources instead of stopping them.

When you hibernate an instance, Amazon EC2 signals the operating system to perform hibernation (suspend-to-disk). Hibernation saves the contents from the instance memory (RAM) to your Amazon Elastic Block Store (Amazon EBS) root volume. Amazon EC2 persists the instance's EBS root volume and any attached EBS data volumes.

The addition of this new feature does not affect the functionality of the nOps Scheduler, it simply adds more diversity into the nOps Scheduler. The scheduling process overall is still the same as it was before. You can create a schedule directly from the nOps Scheduler, or you can use the nOps ShareSave - Resource Scheduler recommendations to automatically configure the recommended schedules.

To learn more, visit our website or read the documentation.