Node Actions

Use this page to understand node actions in MyAccount, when actions are available, what each action changes, and what to check before confirming.

Actions are available from the node list and node details page. The portal enables or disables each action based on node state, node family, operating system, project permissions, region, attached services, and billing state.

note

The action menu is not the final validator. System validation also checks lock state, stopped state, supported node family, Disaster Recovery role, abuse restrictions, older node type restrictions, and whether the requested action is allowed for the current node state.

Start Power Off Stop Reboot Reinstall Save Image Snapshot Upgrade Plan Root Storage Move Project Convert to Committed Lock / Unlock Accidental Protection Recovery Mode Compliance Bulk Actions Delete

---

Availability Reference

This page explains what each node action does. For the central list of states, services, and limits that can make an action hidden, disabled, or rejected, see Node Action Availability and Blockers.

Run a Node Action

Most node actions follow the same portal pattern:

1. Open Compute > Nodes.
2. Find the node in the node list, or select the node name to open the node details page.
3. Open Actions for the node.
4. Select the required action.
5. Review the confirmation dialog, including billing, data-loss, lock, backup, IP, committed-plan, or recovery warnings.
6. Select any required acknowledgement checkbox.
7. Confirm the action.
8. Wait for the node status to update before starting another action.

If an action is visible but disabled, refresh the node and check Action Availability. The portal can disable actions while the node is locked, stopped, in Recovery Mode, a Disaster Recovery target, or already running another operation.

The individual action flows below assume you are already using the selected node's Actions menu unless a flow explicitly refers to the node list, a tab, or a separate plan page.

Start

Use Start to power on a Powered off node or start a Stopped E1-series node.

For standard nodes, Start is usually available from Powered off state. For E1-series nodes, Start is also shown from Stopped state.

Starting from Stopped can take longer than starting from Powered off because the node must be allocated again.

To start a node:

1. For a Powered off node, select Start. For E1-series nodes, Start can also be shown when the node is Stopped.
2. In the Start Node dialog, verify the node name.
3. Select Start Node.
4. Wait for the node to move through the start process and return to Running.

Power Off

Use Power Off to shut down a running node while keeping it allocated.

warning

Powering off a node does not stop node billing. You continue to pay for the node until it is stopped where supported or deleted. Attached resources can continue billing independently.

When a node is powered off, actions such as Start, Save Image, Move to Another Project, Convert to Committed, Lock/Unlock, Recovery Mode, and Delete can remain available when valid.

To power off a node:

1. For a Running node, select Power Off.
2. Read the billing and data-loss warnings in the Power Off Node dialog.
3. Select the acknowledgement checkbox.
4. Select Power Off.
5. Wait for the node status to change to Powered off.

Stop

Use Stop where the portal supports deallocating the node from the underlying host.

For E1-series nodes, Stop can be available from Running or Powered off state. Stop moves the node through Stopping and then to Stopped.

	Power Off	Stop
Allocation	Node remains allocated.	Node is deallocated where supported.
Compute billing	Continues.	Pauses for stopped-node.
Start time	Usually faster.	Usually slower because allocation is required.
Actions while inactive	More actions remain available.	Most actions are unavailable until the node is started.

note

Storage, public IPs, Add-on IPs, backups, snapshots, licenses, and other attached services can continue billing even when compute billing is paused.

Stop is available only for supported custom-root-storage node families. If Stop is not visible or returns an error, check Action Availability.

For E1-specific Stop behavior, see E1 Series Nodes.

To stop an E1-series node:

1. For an eligible E1-series node in Running or Powered off state, select Stop.
2. Read the Stop Node dialog. It explains that compute charges pause while storage and attached add-ons can continue billing.
3. Select the acknowledgement checkbox.
4. Select Stop.
5. Wait for the node status to change to Stopped.

Reboot

Use Reboot to restart a running node without reinstalling the image.

Use Reboot for normal restart workflows. Use Reinstall only when the operating system image needs to be rebuilt.

To reboot a node:

1. For a Running node, select Reboot.
2. Read the warning about disk-intensive workloads in the Reboot Node dialog.
3. Select the acknowledgement checkbox.
4. Select Reboot.
5. Wait for the node to complete the reboot.

Reinstall Node

Use Reinstall Node when you need to reinstall the node image.

warning

Reinstall can affect data and operating system configuration. Back up important data before confirming.

After reinstall starts, the node moves into Reinstalling state and other actions are blocked until the operation completes.

To reinstall a node:

1. Back up important data and create a saved image or snapshot if appropriate.
2. Select Reinstall Node.
3. Read the Reinstall OS dialog. It warns that node data and additional licenses can be removed during reinstallation.
4. Select the acknowledgement checkbox.
5. Select Reinstall.
6. Wait for the node to leave Reinstalling state before using other actions.

If Accidental Protection is enabled, disable it before attempting reinstall.

Save Image

Use Save Image to create a reusable image from a node.

For most flows, the node must be powered off before image creation. Some supported node families can create a saved image without powering off because they use the supported snapshot-based image path.

For the manage-level image guide, see Node Images.

To save an image from a node:

1. Select Save Image.
2. In the Save Image dialog, review the storage charge and root-disk-only note.
3. Enter a saved image name using only letters, digits, underscores, and hyphens.
4. Select Save Image.
5. Wait for the image-saving process to complete before starting another node action.

Create Snapshot

Use Create Snapshot to capture a point-in-time copy of node storage when the node family and current state support it.

For the full snapshot workflow, see Node Snapshots.

To create a snapshot from the action menu:

1. Select Create Snapshot.
2. In the Create Snapshot dialog, keep the generated snapshot name or enter a new name using only letters, digits, underscores, and hyphens.
3. Select attached volumes if you want volume snapshots included.
4. Review the snapshot price note.
5. Select Create Snapshot.
6. Track progress from the node Snapshots tab.

Upgrade or Update Node Plan

Use Upgrade Node Plan or Update Node Plan when the node is eligible for a plan change.

For E1 plan changes, the portal can label the action as Update Node Plan. For E1-specific behavior, see E1 Series Nodes.

To upgrade or update a node plan:

1. Select Upgrade Node Plan or Update Node Plan.
2. On the plan page, review Current Configuration.
3. Use the vCPU, RAM, and, for E1-series nodes, storage filters if needed.
4. Select the target plan.
5. In the confirmation dialog, review the current plan, target plan, pricing, committed-plan impact where applicable, discount or coupon note, and saved-image recommendation.
6. Select the acknowledgement checkbox.
7. Select Upgrade.
8. Wait for the portal to return to the compute page and for the node status to settle.

note

For non-E1 series, the confirmation warns that you cannot change to a lower configuration after upgrading. E1-series update flows can allow a lower plan where the E1 rules permit it.

Increase Root Storage

Use Increase Root Storage to increase root disk size for supported E1-series nodes.

The action is available only when the node is Running or Powered off and validation accepts the request.

For root storage limits, IOPS behavior, and upgrade requirements, see E1 Series Nodes.

To increase E1 root storage:

1. Select Increase Root Storage.
2. In the drawer, review the current plan and disk size.
3. Choose the new storage value with the slider or enter Storage Size (GB).
4. Review the displayed IOPS and estimated cost difference.
5. Select Upgrade Storage.
6. Wait for the storage update to complete before starting another action.

Move to Another Project

Use Move to Another Project to transfer an eligible node to another project within the same CRN.

Attached public IPs, Add-on IPs, backups, volumes, and saved images associated with the node can move with the node when the transfer is valid. Review the confirmation before proceeding.

To move a node to another project:

1. Select the project transfer action.
2. Review the portal notes for attached reserved IPs, backups, volumes, and saved images.
3. Resolve any transfer blockers shown by the portal, such as attached VPCs, multiple security groups, EFS association, tags, or invalid node state.
4. Select the destination project and confirm the transfer.
5. Wait for the node to appear in the destination project.

Convert to Committed Node

Use Convert to Committed when an on-demand node is eligible for committed billing.

Committed billing usually requires a fixed commitment period and an upfront deduction. Review the confirmation, committed period, renewal option, and estimated cost before continuing.

For the dedicated guide, see Committed Nodes.

To convert a node to committed billing:

1. Select Convert to Committed.
2. In the Committed Node Conversion dialog, read the committed billing note. Auto-renewal is enabled by default.
3. Choose a committed option.
4. Review the agreement text and available infra-credit balance.
5. Select the agreement checkbox.
6. Select Convert.

To update committed settings for an already committed node:

1. Select Committed node settings.
2. Review the committed period, committed rate, and committed end date.
3. Choose the preference that should apply after the committed period ends: auto-renew, hourly billing where available, or auto deletion where available.
4. Select Update Settings.

Lock Node and Unlock Node

Use Lock Node to prevent most mutating actions on a node. Locking does not stop the workload or block SSH, RDP, VNC, or published services.

When a node is locked, actions such as save image, start, power off, delete, reboot, reinstall, rename, upgrade, committed settings, IPv6 attach or detach, and project transfer can be disabled.

Use Unlock Node when you need to perform management actions again.

note

Locking a node can affect scheduled node and volume snapshot actions. Review scheduled actions after locking or unlocking a node.

Lock or Unlock a Node

Use the node lock option to prevent important node actions from being performed accidentally.

To lock or unlock a node:

1. Open the node details page.
2. Select the lock status action:
   • Select Lock Node if the node is currently unlocked.
   • Select Unlock Node if the node is currently locked.
3. Review the confirmation dialog.
   • When locking a node, review the list of actions that locking disables, including save image, start or power off, delete, reboot, reinstall, rename, upgrade, committed settings, IPv6 attach or detach, and project transfer.
   • When unlocking a node, review the list of actions that unlocking enables again.
4. Review the note about snapshot scheduling, if shown.
5. Confirm the action by selecting:
   • Lock Node to lock the node.
   • Unlock Node to unlock the node.

Accidental Protection

Accidental Protection is a safety setting that blocks destructive or disruptive actions such as delete and reinstall.

Use it for production or important nodes where an extra confirmation layer is needed. Disable it only when you intentionally need to delete or reinstall the node.

For the detailed workflow, see Node Security.

To enable or disable Accidental Protection:

1. Select Enable Accidental Protection or Disable Accidental Protection.
2. Verify the node name in the dialog.
3. Select Enable or Disable.

Recovery Mode

Recovery Mode starts a supported powered-off Linux node with a recovery environment so you can repair access, boot, or filesystem issues.

Recovery Mode requires a supported OS and Powered off state. It is not shown for Windows nodes, FortiGate nodes, spot nodes, or unsupported states.

For the detailed workflow, see Node Security.

To enable or disable Recovery Mode:

1. Power off the node.
2. Select Enable Recovery Mode or Disable Recovery Mode.
3. Verify the node name in the dialog.
4. Select Ok.
5. Wait for the recovery-mode status to update before starting the node or continuing repair work.

If the node is not powered off, the portal can show an information message asking you to power off the node first.

Security Compliance

Security Compliance registers an eligible node for host-level security monitoring and provides access to security analysis dashboards.

Enable and disable actions are available only for eligible nodes and locations. For eligibility checks, see Action Availability.

For the detailed workflow, see Node Security.

To enable Security Compliance from the action menu:

1. Select Enable Security Compliance.
2. Review the monthly charge and service description.
3. Select the acknowledgement checkbox.
4. Select Enable.
5. Copy and run the portal-generated commands inside the node.

To disable Security Compliance:

1. Select Disable Security Compliance.
2. Verify the node name.
3. Select Disable.

Delete Node

Use Delete Node to terminate a node.

danger

Deleting a node is destructive. Review backups, snapshots, saved images, public IPs, Add-on IPs, attached volumes, and application data before confirming deletion.

The delete flow can ask whether to retain or release related resources such as public IPs, Add-on IPs, and backup data. Review each option carefully before confirming.

To delete a node:

1. Back up required data and confirm whether you need saved images, snapshots, volumes, public IPs, Add-on IPs, or CDP backup data.
2. Select Delete Node.
3. Read the Delete Node dialog, including data-loss, license, committed-node, public-IP, snapshot, backup, and compliance warnings where shown.
4. Choose whether to retain eligible backup or IP resources when the dialog offers those options.
5. Select the acknowledgement checkbox.
6. Select Delete.
7. Wait for termination to complete.

If Accidental Protection is enabled, disable it before attempting delete.

Bulk Actions On Nodes

Bulk actions let you perform selected actions on multiple nodes at once.

Supported bulk actions include:

• Power Off
• Start
• Reboot
• Lock
• Unlock

info

Bulk actions can be performed on a maximum of 10 nodes at a time.

To perform a bulk action:

1. From the node list, select the nodes you want to act on.
2. Select Bulk Actions.
3. Choose the action.
4. Review the valid and invalid node lists in the confirmation dialog.
5. Select the acknowledgement and confirm the action.

The confirmation dialog separates nodes where the action can run from nodes where it cannot run. Nodes can be invalid for a bulk action because of state, lock status, recovery mode, Disaster Recovery role, stopped state, unsupported node family, or other service constraints.

API and Automation

You can also manage nodes through the MyAccount API after creating an API token.

Common node management API surfaces include:

Task	API surface
List or create nodes	GET /api/v1/nodes/, POST /api/v1/nodes/
Get node details	GET /api/v1/nodes/{node_id}/
Delete a node	DELETE /api/v1/nodes/{node_id}/
Convert a node to committed billing	POST /api/v1/nodes/{node_id}/
Run a node action	PUT /api/v1/nodes/{node_id}/actions/
Run a bulk node action	PUT /api/v1/nodes/action-on-multiple-nodes/
Access VNC or console data	GET /api/v1/nodes/vnc/{node_id}
Upgrade node plan	PUT /api/v1/nodes/upgrade/{node_id}
Increase root storage	PUT /api/v1/nodes/{node_id}/root-storage-upgrade/
View attached volumes	GET /api/v1/nodes/{node_id}/attached-volumes/
View network details	GET /api/v1/nodes/{node_id}/networkdetail/
Manage snapshots	GET /api/v1/nodes/{node_id}/snapshots/, POST /api/v1/nodes/{node_id}/snapshots/
Manage scheduled actions	GET /api/v1/nodes/{node_id}/scheduled_actions/, POST /api/v1/nodes/{node_id}/scheduled_actions/

See the MyAccount API reference for the approved public API schema.

warning

Use the published API reference as the source for supported request fields. Portal-only fields or internal implementation details can change without notice.

---

Related Resources

Resource	Use it for
Manage Nodes	Return to the node management overview.
Node Network	Manage IPs, VPCs, and network attachments.
Node Security	Manage SSH keys, recovery mode, accidental protection, and compliance.
Action Availability	Check why actions are hidden, disabled, or rejected.
Node Images	Understand saved images.
Node Snapshots	Understand snapshots.
E1 Series Nodes	Manage E1-specific Stop and root storage behavior.

---