Skip to main content

Managing SSH Configurations

This section describes how SSH configurations are created, modified, and applied to hosts.

SSH configurations are managed via the Hosts → SSH Configurations page.

You can View an SSH configuration to see the contents of the associated configuration file. Note that discovered SSH software configurations are initially placed in the monitored state. An SSH configuration must be switched to the managed state before it can be edited. Switching a host to managed state also switches its configurations to managed state. Any hosts not in managed state will keep the monitored configuration.

Making a monitored configuration managed will assign the new managed copy to managed hosts using that specific revision. If there are multiple revisions of the monitored configuration, each of them needs to be made managed separately. When no hosts are using any of the monitored configuration's revisions, the configuration will be automatically marked as deleted.

Alternatively, you can duplicate a configuration as a managed copy, and assign it to the hosts. When you save your edits to a configuration, the revised configuration is saved as the latest revision of that configuration.

Modifications to SSH configurations do not automatically take effect. For the modified settings to take effect, they must be assigned and deployed to hosts.

For instructions about assigning and deploying configurations, see Deploying SSH Configurations to Hosts.

note

On agentless hosts, the SSH server port cannot be changed.

A new SSH configuration can be created in one of the following ways:

  • duplicating an existing, managed SSH configuration

  • creating a new configuration from scratch

SSH configurations can only be deleted if they are not assigned to any host. Before you can delete a configuration, you must first assign its hosts to other configurations.