nOps PROD Product Announcements logo

Product Announcements

Back to Homepage Subscribe to Updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement

Jump to Month

  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • July 2021
  • December 2020
  • September 2020
Powered️ byAnnounceKit

Create yours, for free!

a year ago

Introducing EC2 Resource Auto-Detection

Compute Copilot makes it easy to save with Spot, bringing Spot market insights and awareness of your commitments to your ASGs. 

Copilot automatically and continuously tunes your configurations to ensure you’re (1) fully utilizing your commitments, and (2) always on the most cost-effective and reliable option available.

EC2 resource requirements are now automatically derived from prior ASG Launch Template configurations

Now, as Copilot moves your instances onto cost-effective and stable Spot, it will automatically ensure replacement instances are memory- and CPU-compliant. 

Simply select instance families for Copilot to use, and it will intelligently detect and apply minimum vCPU and RAM requirements from your prior ASG Launch Template configurations. As a result, there’s no longer any need to keep track of your workload requirements — Copilot fills in the correct parameters on the fly for seamless and reliable Spot savings.

If you prefer to exert granular control, you can also exercise the option to define exact parameters.

How it works:

When AWS ASG launches an On-Demand instance (e.g. m5.4xlarge):

  • Lambda intercepts the instance launch event
  • Determines the instance vCPU (16) and RAM (64 Gib) options
  • Finds the cheapest stable instance type based on: instance families selected, vCPU and RAM options, nOps Spot recommendations
  • Replaces On-Demand instance m5.4xlarge with the same or higher size Spot instance

For additional details, please consult the documentation. 

At nOps, our mission is to make it easy for engineers to optimize, so they can focus on building and innovation.

Copilot is built on your existing AWS-native ASGs. As a result, it’s ultra-easy to onboard and offboard. Simply plug it in to effortlessly run mission-critical workloads with peace of mind that you are scheduled on the most cost-optimized and stable option at all times. 

Join our customers using Copilot to cut cloud costs and leverage automation with complete confidence by booking a demo today!

Avatar of authornOps
Announcement
a year ago

Compute Copilot Now Supports Cluster Autoscaler

As many tech organizations shift more resources to Kubernetes, cost-optimizing EKS is increasingly crucial. Yet, teams often lack the time and sophisticated tools needed to continually monitor and optimize cloud resources.

Recognizing this need, Compute Copilot now supports the two leading native AWS node management frameworks (Cluster Autoscaler and Karpenter) for a hands-off approach to workload management. 

Copilot automates the scheduling and scaling of your workloads for maximal stability, time savings, and cost savings — ensuring you are always on optimal cloud resource combinations with minimal engineering intervention.

Copilot makes it easy to save with Spot, while upholding the utmost standards of reliability.

Using Spot safely with Cluster Autoscaler can be a complex and time-consuming task, involving challenges like: 

  • Spot interruptions disrupting workloads
  • Continually shifting price and capacity in the Spot market
  • The need to repeatedly balance Spot usage with existing Savings Plan and Reserved Instance commitments

Copilot navigates these challenges seamlessly on your behalf. Every 10 minutes, it analyzes the Spot market to predict termination 60 minutes in advance. It then automatically and continually moves your workloads onto diverse and less risky instance types, minimizing your risk of interruption. This proactive approach allows you to benefit from Spot savings, with enterprise-level SLAs for reliability. 

Copilot offers automated real-time instance reconsideration

Copilot continually monitors your dynamic usage and your existing SP and RI commitments, ensuring you are on the most cost-effective and stable blend of compute resources possible at all times.

At nOps, our mission is to make it easy for engineers to cost optimize, so they can focus on building and innovating. With the platform, there’s no longer a reason to manually manage workloads; Copilot does it for you more effectively and at a lower cost. 

And there’s no vendor lock-in — Copilot updates configurations in your AWS-native tools,  meaning no major architecture update is needed to onboard or offboard. Plug it in or walk away at any time.

  1. Scaling Operation: Cluster Autoscaler triggers a scaling operation by adjusting the DesiredCapacity of the ASG.
  2. Compute Copilot Lambda Activation: Whenever the ASG launches a new on-demand instance (e.g., in response to a desired capacity change), the Compute Copilot Lambda is activated.
  3. Spot Instance Launch: The Compute Copilot Lambda responds by automatically launching a Spot instance configured to mirror the settings of the On-Demand instance.
  4. Attachment to ASG: The Spot instance is seamlessly attached to the Cluster, confirming its serviceability.
  5. Graceful Pod Removal: The Compute Copilot Lambda communicates with the Compute Copilot Agent running in the EKS Cluster to gracefully remove pods from the On-Demand instance before termination, preserving the integrity of your EKS environment.
  6. On-Demand Instance Removal: The Compute Copilot Lambda terminates the corresponding On-Demand instance, completing the migration process.

For more on how to use Copilot and how it works, please consult the documentation. 

nOps was recently ranked #1 in G2’s cloud cost management category.

Join our customers using nOps to cut cloud costs and leverage automation with complete confidence by booking a demo today!



Avatar of authornOps
a year ago

New CloudWatch Integration Delivers Instant Rightsizing Savings

Rightsizing your EC2 instances plays a critical role in containing costs and fully harnessing the potential of your AWS resources. However, collecting the data needed to effectively rightsize can be difficult and time-consuming. 

nOps now integrates with your AWS-native CloudWatch, for effortless rightsizing savings. We now automatically analyze every EC2 instance in your environment for CloudWatch recommendations, which you can apply with one click on the platform.

For high-resolution recommendations, we also automatically ingest enhanced CloudWatch data from every instance with  CloudWatch Agents. Real-time coverage of resource-level insights such as memory, CPU, network bandwidth, volume size, and more are fed into nOps’s state-of-the-art ML engine — for the most reliable rightsizing recommendations.

Rightsizing with nOps for:

  • The best rightsizing recommendations available. nOps automatically collects and analyzes highly granular data, for 100% accurate and reliable rightsizing recommendations.
  • Significant time savings. nOps integrates with the two most popular AWS monitoring solutions (CloudWatch Agent or Datadog) and EventBridge. It automates the complex and time-consuming rightsizing process into a single click — freeing up engineers to build and innovate.
  • Up to 50% in immediate cost savings. When engineers don’t act on rightsizing recommendations, underutilized and idle resources continue to drive unnecessary AWS costs. nOps make it completely pain-free and effortless for engineers to actually act on recommendations and start saving.


How it works

1.nOps integrates with your CloudWatch or CloudWatch Agent to collect all of the metrics needed for rightsizing recommendations, based on your last 15 days of usage. Our API queries your data every 24 hours and saves it in S3. 

CloudWatch metrics used for rightsizing

2. We quickly and efficiently process huge amounts of data from S3, cross-referenced with AWS EC2 metadata and the latest AWS On-Demand pricing data. These three sources of data are combined and fed through a Rightsizing Engine, to accept or reject each individual EC2 instance based on its utilization (resulting in recommendations for only underutilized resources). 

Each of your instances is analyzed taking all relevant info into account, such as the metrics necessary for your particular operating system. For each instance in your environment, we make the following calculations:

  • Max Disk usage
  • Max Network usage
  • Max RAM utilization (depending on which version you have)
  • Max CPU utilization

Our rightsizing algorithm compares maximum recorded usage against the capacity of a lower instance type, multiplied by a threshold value that accounts for potential future usage spikes. AWS Recommends using 80% of the lower size’s capacity as a benchmark. 

3. These rightsizing recommendations are then pushed to nOps microservices, which are responsible for showing recommendations from the nOps platform on the UI. 

The nOps dashboard shows your rightsizing savings

4. Every 24 hours the process runs from top to bottom. 


About nOps 

nOps was recently ranked #1 in G2’s cloud cost management category.

Join our customers using nOps to cut cloud costs and leverage automation with complete confidence by booking a demo today!

Avatar of authorSwapnalee Patil
Announcement
a year ago

nOps Launches Karpenter .33 Beta Support, Fueling Savings On Any Version

Compute Copilot is an intelligent workload provisioner that continuously manages, scales, and optimizes your EKS compute for the best cost and stability. Copilot is built on Karpenter for its latest-gen scheduling capabilities and seamless integration with cost-effective Spot Instances.

The Karpenter .33 Beta Release brings significant changes, notably transitioning from Provisioners and Node Templates to a more streamlined architecture of NodePools and NodeClasses. This change significantly alters the structure of Karpenter configuration files. For more on the changes and why they matter, check out our recent blog detailing all of the new Karpenter beta capabilities.

In this latest release, nOps Compute Copilot fully supports these advancements while ensuring backward compatibility with earlier Karpenter versions. Users can now effortlessly use Copilot regardless of your Karpenter version and upgrade at your convenience. Our backend handles all of the changes hassle-free on your behalf.

How it works:

  1. We have upgraded the agent installed on client clusters. This agent is responsible for sending the CRUD commands to the Kubernetes API, choosing the proper CustomResources (NodeTemplates/NodeClasses or Provisioners/NodePools).
  2. We have enhanced our API to validate the CustomResources based on the version. Therefore, we added a new set of validators for the NodeClasses and the NodePools. 

Compute Copilot now supports NodePools and NodeClasses

Whether your clusters operate on older or newer versions of Karpenter, or a combination of both, Compute Copilot is meticulously engineered to support you. 

Find out how Copilot makes it simple and easy to update to Karpenter .33 Beta in the documentation, which offers detailed information about the changes and upgrade procedures.

Avatar of authornOps
a year ago

nOps Unveils History of Actions Dashboard: Track Instance Replacements and Cost-Saving Changes Effortlessly

Compute Copilot constantly monitors the Spot market and your dynamic usage, automatically tuning your ASG configurations with no effort on your part for cost savings.

The latest update to Copilot for ASG features a new History of Actions Dashboard. It makes it easy to understand how Copilot is cost-optimizing your instances and how much money you are saving. 

You benefit from:

  • Detailed workload tracking. View all the instances that were replaced by Copilot, and what they were replaced by.
  • Cost impact analytics. Quickly understand the effectiveness of replacements and how long they ran.


Not yet using Compute Copilot to manage ASGs? It just takes a couple of quick tags to onboard and start realizing effortless ASG savings. 

Avatar of authornOps
a year ago

Maximize Savings On Mixed-Instance ASGs


If you’re currently using Spot to save on your ASG costs, you’re familiar with the complexity and time needed to cost-optimize your commitment usage and choosing the best Spot instances for your workloads. 

Compute Copilot was created to make it easy to save, bringing Spot market insights and awareness of your commitments to your Mixed-Instance ASGs. It automatically and continuously tunes your ASG configurations to ensure you’re (1) always using the right amount of Spot, and (2) always on the most cost-effective and reliable option available, gracefully replacing your nodes before termination.

And because it’s built on your existing AWS-native ASGs, it’s ultra-easy to onboard. Simply plug it in to effortlessly run mission-critical workloads with peace of mind that you are scheduled on the most cost-optimized and stable option at all times. 

New Mixed-Instance Policy & Lifecycle Hook Support

For hassle-free savings on the full range of your ASGs, Copilot now optimizes: 

  • ASGs with Mixed Instance Policies — Launch multiple instance types and On-Demand Instances and Spot Instances within a single Auto Scaling group.
  • ASGs with Lifecycle Hooks — Create solutions that are aware of events in the Auto Scaling instance lifecycle, and then perform a custom action on instances when the corresponding lifecycle event occurs.


It just takes a couple of quick tags to onboard and start realizing effortless Spot savings on all of your ASGs.

At nOps, our mission is to make it easy for engineers to optimize cost. Learn more about how Compute Copilot can help you save while freeing up your time to focus on building and innovation. 

How It Works

The below diagram provides additional information on how Copilot optimizes your ASGs.

ASG launches a new on-demand instance

Lambda intercepts the EC2 Instance State-change Notification event from EventBridge

If the created instance is not protected from termination and should be replaced, Compute Copilot performs the following steps:

  1. Copy the Launch Template or Launch Configuration from the ASG launch template
  2. In the copied Launch Template, modify Network Interfaces, Tags, Block Device and/or Mappings from the instance Launch Template or Configuration if needed
  3. Fetch recommended instance types from nOps API
  4. Request Spot Fleet with the copied Launch Template and recommended instance types
  5. Once the Spot request is fulfilled, get the Spot Instance and wait for it to its state to be Running
  6. Attach the created Spot Instance to the ASG
  7. Wait for the attached Spot Instance’s state to be InService
  8. If there is a lifecycle hook for termination for On-Demand, the On-Demand will go through the lifecycle hook action for termination
  9. Terminate the On-Demand instance
  10. If there is a Mixed-Instance Policy, modify the percentages of On-Demand and Spot accordingly.  

For more information, you can also consult the documentation.

Avatar of authornOps
a year ago

nOps Expands Right Sizing to Hibernated & EBS Encrypted Instances


With nOps, it’s as simple as integrating your existing utilization and monitoring tools to start right sizing and shrinking your AWS bill. 

Today, we’re announcing a new feature helping you save more by effortlessly right sizing even the most complex of instances. nOps now supports: 

EBS Encryption: Right sizing instances with security and compliance requirements is normally a time-consuming and complex process, involving stopping the instance, fetching a key, de-encrypting, right sizing, re-encrypting, and restarting each instance. nOps now seamlessly integrates with AWS's key management to put it all on autopilot, making it extremely easy to right size. 

Hibernation: nOps now automatically right sizes Hibernation enabled instances, for occasions when you need to save the state of your EC2. Delegate the normally complicated and annoying process of disabling each instance without losing any data, right sizing, and restarting  — freeing up your time to build and innovate.

Let’s take a look at the benefits of automated right sizing with nOps. 

  • Fully trustworthy recommendations. Often, engineers don’t implement right sizing recommendations because they don’t trust them. By automatically collecting comprehensive data on your memory, CPU, storage, and networking through your existing monitoring solution (Datadog, CloudWatch…), nOps right sizing recommendations are highly trustworthy.



Visualize right sizing recommendations in an easy-to-scan dashboard.

  • Significant time savings. Simply integrate your existing monitoring solution, review recommendations, and one-click apply via automation. nOps makes it pain-free to right size in seconds to eliminate underutilized and idle resources driving unnecessary AWS costs.
  • Expanded cost savings. With the new release, you’re no longer limited to saving on “vanilla” EC2 — you can right size Encrypted and Hibernated instances for more effort-free AWS savings.

nOps was recently ranked #1 in G2’s cloud cost management category. Join our customers using nOps to slash your cloud costs and leverage automation with complete confidence by booking a demo today!

Avatar of authornOps
Announcement
a year ago

New Configure-by-Tag for Ultra Easy Onboarding

Today, we’re announcing Configure-by-Tag: a new feature making it as easy as possible to onboard to Compute Copilot for ASG and start saving. 

The feature brings you:

  • Effortless integration via any IaC tool. IaC integration eliminates all the manual work of managing ephemeral ASGs through redeployments. Once you onboard with a quick tag, you’re completely done — create, destroy, recreate ASGs, and they will be automatically configured for Compute Copilot.

  • Centralized management of configurations. Configure-by-Tag makes bulk management of ASG configs simple. A single template can manage all the configuration options for as many ASGs as desired.
  • Automatic Spot savings. Once you Configure-by-Tag, Compute Copilot for ASG will automatically put you on the most stable and cost-optimized Spot instance types — for effort-free continual cost reduction. 

You can observe instance replacements and ASG configurations reflected in the UI. For more specifics on how it works, check out the full documentation.

At nOps, our mission is to make it easy for engineers to cost optimize by seamlessly integrating with your preferred tools and services.

Learn more about how Compute Copilot can help you save while freeing up your time to focus on building and innovation. 


Avatar of authornOps
a year ago

New YAML Support for Karpenter

Compute Copilot for EKS integrates with Karpenter to automatically reduce your AWS bill. 

It now supports YAML configurations, in the latest update for flexibility and ease of use. In response to customer request, this release offers:

Effortless onboarding. YAML configuration makes it ultra easy to onboard your Karpenter-managed cluster to Copilot via UI or API. Simply import your current configurations to migrate to modern Karpenter and put your node provisioning on autopilot.

Full control. Whether you want to delegate your configurations to nOps or exercise granular control, YAML configuration unblocks all Karpenter-supported configuration options.

Check out these videos with nOps Engineers Hayk Harutyunyan and Thiago Carvalho for more information on the new YAML support options, what they are, and why you should use them.


For more on the feature release and Compute Copilot, check out the full announcement here. 

Avatar of authornOps
a year ago

nOps & Datadog Partner to Supercharge Your Rightsizing Cost Savings

Spend reduction is a top priority in today’s economic climate. And for businesses leveraging AWS and EC2, rightsizing plays a critical role in containing costs and fully harnessing the potential of your resources. Many tools offer rightsizing recommendations, but engineers often don’t act on them. That’s because:

Rightsizing recommendations are frequently wrong. Reliable recommendations require granular historical data on memory, utilization, network bandwidth, volume size, and more. This data is difficult to collect and analyze. As a result, engineers don’t trust recommendations are accurate, and don’t act on them. 

Acting on recommendations is complex and incredibly time-consuming. Cumbersome resource investigation, ticketing processes, manually editing Terraform and more means rightsizing initiatives can be a multimonth IT resource time sink.

Datadog and nOps to the rescue

To make rightsizing easier and more effective for teams, Datadog and nOps have partnered together. Via a one-click integration with no additional costs or steps, nOps builds on the end-to-end visibility provided by Datadog to revolutionize your rightsizing and commitment management.

Datadog’s cloud monitoring and analytics provides engineers with real-time coverage of resource-level insights such as memory, CPU, and storage — granting nOps full visibility into the exact data needed for 100% accurate rightsizing recommendations. 

nOps’s automated FinOps platform then makes it insanely easy for engineers to take action. Via integration with your tools and frameworks (Terraform, Eventbridge…), nOps fully automates months of work to apply recommendations into mere seconds. 

Here’s how this natural partnership is changing the game. It grants you:

Complete Rightsizing Confidence. Datadog’s comprehensive logging and monitoring data is fed into nOps’s state-of-the-art ML engine. These data-backed recommendations are visualizable in an easy-to-scan dashboard which proves reliability and accuracy to engineers beyond a shadow of a doubt — giving them the confidence to act on recommendations.

Hours of Time Savings. With the platform, it takes five seconds to make a changeset, accept the changeset, and push it out. nOps automates away all the work and complexity, freeing up engineers to focus on other meaningful projects. One click to accept the recommendation and you are done.

Vast Cost Savings. When engineers don’t act on rightsizing recommendations, underutilized and idle resources continue to drive unnecessary AWS costs — leading to thousands in missed savings accumulating every day. nOps make it completely pain free and effortless for engineers to actually act on recommendations for up to 50% in immediate cost savings. 

Hands-off commitment management. Once you accept rightsizing recommendations, nOps automatically provisions and deprovisions commitments into your environment. As a result, you benefit from the savings of SPs, with all the flexibility of on-demand.

nOps was recently ranked #1 in G2’s cloud cost management category — and together with Datadog, the savings are reaching new heights.

Avatar of authornOps