Skip to content

Commit c9f538f

Browse files
authored
Update security-best-practices.md
1 parent 2ed4fbf commit c9f538f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/batch/security-best-practices.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Batch security and compliance best practices
33
description: Learn best practices and useful tips for enhancing security with your Azure Batch solutions.
4-
ms.date: 08/08/2024
4+
ms.date: 11/19/2024
55
ms.topic: conceptual
66
---
77

@@ -69,7 +69,7 @@ Batch management operations via Azure Resource Manager are encrypted using HTTPS
6969

7070
### Batch pool compute nodes
7171

72-
The Batch service communicates with a Batch node agent that runs on each node in the pool. For example, the service instructs the node agent to run a task, stop a task, or get the files for a task. Communication with the node agent is enabled by one or more load balancers, the number of which depends on the number of nodes in a pool. The load balancer forwards the communication to the desired node, with each node being addressed by a unique port number. By default, load balancers have public IP addresses associated with them. You can also remotely access pool nodes via RDP or SSH, see [Configure remote access to compute nodes in an Azure Batch pool](azure/batch/pool-endpoint-configuration).
72+
The Batch service communicates with a Batch node agent that runs on each node in the pool. For example, the service instructs the node agent to run a task, stop a task, or get the files for a task. Communication with the node agent is enabled by one or more load balancers, the number of which depends on the number of nodes in a pool. The load balancer forwards the communication to the desired node, with each node being addressed by a unique port number. By default, load balancers have public IP addresses associated with them. You can also remotely access pool nodes via RDP or SSH, see [Configure remote access to compute nodes in an Azure Batch pool](pool-endpoint-configuration).
7373

7474
#### Batch compute node OS
7575

@@ -158,7 +158,7 @@ For more information, see [Create a pool without public IP addresses](simplified
158158

159159
#### Limit remote access to pool nodes
160160

161-
Pools created using API version earlier than `2024-07-01`, Batch by default allows a node user with network connectivity to connect externally to a compute node in a Batch pool by using RDP or SSH. You can limit the remote access by creating you pools using API with version `2024-07-01` or later.
161+
For pools created using an API version earlier than 2024-07-01, Batch by default allows a node user with network connectivity to connect externally to a compute node in a Batch pool by using RDP or SSH. You can limit the remote access by creating you pools using an API with version 2024-07-01 or later.
162162

163163
To limit remote access to nodes in pools created by API with version earlier than `2024-07-01`, use one of the following methods:
164164

0 commit comments

Comments
 (0)