Through the rapid evolution of the cloud, workloads have become the foundational unit of business value in the cloud. These collections of resources might use common architectural patterns, have common compliance goals, or be owned by specific teams and stakeholders.

nOps continues its mission to align every resource in your cloud environment with your business. In nOps workloads, you can define the competencies, lenses, and frameworks that are key to your workload environment in order to get contextual recommendations, targeted assessments, and detailed reports.

Workloads in nOps help you to group different AWS resources that have been created within your AWS environment. This makes it easier to carry out various assessments on those specific services that make up with Workload. You can add new resources to an already existing workload that has been created.

Automatic recommendation 

nOps present the recommendations and path to remediation based on your workload priority. For example, if you select WAFR for the lens, nOps will recommend you to upload a reliability incident playbook. 

Document repository 

As you upload documents related to the workload, nOps organizes all of the documents related to your workload at one place.  

Integrated reports help you to get workload-centric insights, built-in assessments and auto-detection. It walks you through the process of evaluating and creating improvement plans, built-in budgets help you to plan and track your spend, and document repositories help you to track and manage governance in your environment.

The AWS Well-Architected Tool helps you review the state of your workloads and compares them to the latest AWS architectural best practices. The tool is based on the AWS Well-Architected Framework, developed to help cloud architects build secure, high-performing, resilient, and efficient application infrastructure. Well Architected Reviews must be conducted on the production workload on a periodic basis. After conducting the review, you should prioritize the remediation of any identified issues according to your business priorities.

We made some big improvements on how navigation works on nOps. Are you Looking for unused resources or resources that aren’t tagged?  No worries, this information is now available at your fingertips, press + and type what you are thinking about, and we’ll get you there in lighting speed. Go ahead and try clicking 'COMMAND' + 'K' now to see for yourself.

nOps is proud to announce our comprehensive suite of first-class tools is purpose-built to support your cloud compliance with Azure Well-Architected Framework best practices providing you with key metrics that will help you enforce operational accountability.

Seamless Alignment with Azure Well-Architected Best Practices:

Building a well-architected solution is important in maximizing the full benefits Azure Cloud has to offer. nOps’s powerful auto-discovery engine helps your infrastructure comply with best practices of the five pillars of Azure Well-Architected Framework—cost optimization, security, performance, reliability, and operational excellence.

Continuous Resource & Cost Optimization:

Design and architect optimized workloads in the most cost-efficient manner. Rein in sudden cost spikes, capacity issues, and bill shocks by monitoring changes continuously across Azure users, accounts, regions, cloud services, resources, usage types, operations, and tags. All these are presented in a single pane of glass multi-cloud format, empowering you to make informed decisions.

Visibility & Change Management:

Stay in the loop with your constantly evolving infrastructure. nOps provides near-instant visibility to changes in your cloud environment and configuration history, along with continuous notifications of security risks and detailed audit trails. All these are presented in an integrated Single Pane of Glass Dashboard.

Security & Compliance:

Fortify your Azure infrastructure’s security by staying on top of security issues before they cause damages.

Operational Accountability:

Empower your organization’s cloud center of excellence (CCOE) with comprehensive and detailed insights necessary in standardizing and enforcing your cloud governance process.

Get started by adding your Azure account under organization settings and reading more about setting-up permissions here. 

nOps 7.1 Release Cycle Announcement

With the monitoring powers that nOps brings to your infrastructure, it might be a little tricky to organize and manage your communication preferences. 

Change management alerts, rules, dashboards, and reports are different places where you can get notified. We’ve added the option to organize and get on top of your communication preferences on one page to get what you want, when you want it. 

Start organizing your communication preferences by clicking here.

Workloads are your building blocks to manage and improve your infrastructure. 🌏 

With nOps workloads, you can validate and measure the effectiveness of workload resources. Now, you can even get more than that by integrating workloads features with your workflow using nOps APIs for workloads! ⚡  Learn more about how you can pull your workload

Click here for more info

nOps has enhanced the partner sign-up flow. Now partners can be on-boarded and using nOps in minutes. nOps has also added a new dashboard that highlights the major features available on the nOps Partner Portal.

Click to go to partner portal 🚀 

Workloads provide a level of abstraction to describe and group resources

with a well-defined function and purpose to facilitate observation and

management. Once a workload is defined on nOps, a corresponding

workload is automatically created on your AWS account.

Workload type and resources are defined by using filters like Regions or Services.

It’s now possible to receive notifications about rules violations on

dashboards even when not on nOps.

Navigate to your custom dashboard (Reports -> Custom dashboards).

Click ‘Configure Notifications.’

Many resources in AWS have not supported tags upon creation. Now, by

default, tags can be attached to resources so that the root of any

violations can easily be highlighted and managed. 

To access, go to your: Profile Settings -> Default tagging.