Introduction
Hello everyone, it’s your friendly neighborhood Technical Marketing Engineer! This will be the first in a series of blogs meant to introduce the NuService Menu and help administrators transition away from unrestricted Bash access when interacting with their Nutanix environment. You might be thinking, what is this Nutanix NuService menu? That’s a great question and hopefully by the end of this blog I will have done a great job at trying to explain it.
Before we dive into what the NuService menu is, we should probably cover why we are doing this. Much of this can be found in Nutanix KB-2012 “End of Support Life (EOSL) for SSH Bash Shell Access” located on the Nutanix customer portal. To quote the KB directly:
“Direct SSH/Bash shell access is being phased out to further strengthen security, reliability, and long-term supportability. Bash access provides unrestricted system access, which increases security risk and makes long-term support and automation more difficult. Moving to supported interfaces ensures more consistent, auditable, and supportable workflows. Nutanix is actively developing alternative mechanisms, including an enhanced SSH Service Menu, expanded v4 API capabilities, and richer PowerShell support, ensuring administrators retain essential service and troubleshooting access.”
Direct operating-system access can provide elevated privileges, depending on the access path and user context. Nutanix environments use an integrated software and infrastructure architecture in which unsupported operating-system changes may affect system behavior and supportability. Changes outside documented and supported procedures may affect system behavior and supportability. Consult the applicable Nutanix support terms before making such changes. So please take a moment to review the Nutanix Knowledge Base article above, as it goes into greater detail on the why, timelines and a lengthy FAQ to help with this transition.
This blog series will be to walk through the NuService menu and provide details on how to leverage it, along with other Nutanix tools or control planes to obtain details previously gathered when interacting with Bash.
NuService was introduced in our NCI 7.6 release. In applicable configurations, NuService may become the default SSH entry point in a future release. Consult current release documentation for planned behavior. You can control whether SSH access is available for reaching the NuService menu by configuring SSH access to the cluster. To do so via Prism Central from the Infrastructure Menu navigate to Hardware → Clusters and then select a cluster and click on “More”. Here you will see “Enable | Disable NuService Mode”. This controls the overall ability to leverage SSH access to the cluster and subsequently display the new menu when SSH is enabled. If you desire to not allow SSH access at all, you would select the disable option from this drop down in Prism Central. If you select “Enable NuService Mode”, it will allow SSH and enable the new menu that will be covered more below.
In the applicable 7.6 configurations, an SSH session to a Nutanix CVM may be directed to the NuService menu. Behavior depends on release, cluster configuration, and access settings.
So to what cluster configurations will this apply you might ask? The table below will explain under what conditions attempts to SSH will be redirected to this new menu.
For more information on configuring Restricted Access and what you need to be aware of, please see our AOS Security guide on the Nutanix Portal. Restricted access as you can see will redirect both admin and nutanix SSH sessions to the NuService menu. A couple items to note here:
- STIG Compliance - For those who need to meet DISA STIG compliance in 7.6, you will need to follow the steps in the linked security guide to enable restricted access.
- Temporarily enable Bash shell - Should you enable restricted access, it cannot be reversed, so please make sure you have fully evaluated your scripts and any other tooling that leverages direct Bash shell access. Once enabled in 7.6, you can gain temporary access to the Bash shell. It will involve a support engagement to conduct an MFA code exchange. Doing so will result in a 72-hour window where the Bash shell will be enabled. After that time expires a new MFA token exchange with support will need to be initiated.
Now what can I do?
Instead of walking through each of the main menu items, let’s dive right in and show you this new menu. If you would like more information on the different menu options and what they mean, please visit the AOS Security Guide. While this blog and future ones around the same topic are meant to explain what is supported and how to accomplish similar tasks, one question that one might have: What is not supported? That is a great question and a simple answer is anything you don’t see in the product documentation. If in doubt, consult the release product docs and use “help” from any of the prompts listed below to show what is possible.
Let’s walk through a few different ways to use this new menu for operational actions. We will start with the CVM. In order to run commands on the CVM, enter ‘1’ - ‘Execute Commands’ from the initial NuService menu and then ‘1’ again from the next menu selection list for ‘CVM’. This will drop you into a prompt where you can run documented and supported commands in order to interact with the Nutanix Controller Virtual Machine.
What commands are available? If you type “help” from the above <cmd> prompt you will be presented with the supported commands available to run against the CVM. The list is quite extensive, including acli, ncli, cluster start | stop | status, logbay, genesis, ncc, iptables, upgrade_status, afs and many others. Some of these operations correspond to tasks administrators previously performed from Bash, but NuService is not to be confused as providing one-to-one Bash command parity.
To interact with AHV, you will select Option 1 ‘Execute Commands’ and then Option 2 ‘AHV’ from the menu that follows. This will drop you into an AHV prompt that makes available a curated set of supported commands.
What commands are available? Similar to the CVM, if you type “help” from the AHV prompt you will be presented with the available commands. This list isn’t quite as extensive as the CVM. From this prompt you could shutdown the AHV host, view/manage details around networking with a few ovs commands and update the CVM config (ie: name, memory, etc).
Wrapping Up
That just about does it for this introduction to the NuService menu. In future blogs we will highlight how to leverage the NuService menu and where possible doing similar activities with either the v4 API and/or PowerShell. Now is the time to ensure that you review any scripting, tooling and processes that are leveraging the Bash shell. The journey to Nutanix removing direct Bash shell access has begun. Thank you for stopping by and may the secure shell access be with you!
©2026 Nutanix, Inc. All rights reserved. Nutanix, the Nutanix logo and all Nutanix product and service names mentioned are registered trademarks or trademarks of Nutanix, Inc. in the United States and other countries. All other brand names mentioned are for identification purposes only and may be the trademarks of their respective holder(s).
This content may contain express and implied forward-looking statements, including but not limited to statements regarding our plans and expectations relating to new product features and technology under development, the capabilities of such product features and technology, and our plans to release product features and technology. Such statements are not historical facts and are instead based on our current expectations, estimates and beliefs, including statements about NuService development and Nutanix removing direct bash shell access. The accuracy of such statements involves risks and uncertainties and depends upon future events, including those that may be beyond our control, and actual results may differ materially and adversely from those anticipated or implied by such statements, including, among others: failure to develop, or unexpected difficulties, delays or disruptions in developing, releasing or distributing, new products, services, product features or technology in a timely or cost-effective basis.