Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
Login Nodes lifecycle - AWS ParallelCluster

Login Nodes lifecycle

PDFRSS

Currently, there is no dedicated command to stop and start the login nodes in a pool. In order to stop the login nodes in a pool the cluster administrator has to update the cluster configuration specifying zero on the count of login nodes (Count: 0 ) and then run an pcluster.update-cluster-v3 command.

Note

Logged in users are notified about the termination of the specific instance and about the related gracetime period. During the gracetime period no new connections will be allowed except for the ones from the cluster default user. The message shown is customizable by the cluster administrator from the head node or from a login node editing the file  /opt/parallelcluster/shared_login_nodes/loginmgtd_config.json. This termination message is not visible when you are connected using the AWS Systems Manager Session Manager Session Manager.

In order to start the login nodes pool the cluster administrator has to restore the previous Count value in the cluster configuration and then run an update-cluster command.

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.