Skip to content

Commit a3b736c

Browse files
committed
Move image folder
1 parent c183890 commit a3b736c

3 files changed

Lines changed: 2 additions & 2 deletions

File tree

articles/reliability/media/bastion/bastion-instance-zone-traffic.png renamed to articles/reliability/media/reliability-bastion/bastion-instance-zone-traffic.png

File renamed without changes.

articles/reliability/media/bastion/bastion-instances-zones.png renamed to articles/reliability/media/reliability-bastion/bastion-instances-zones.png

File renamed without changes.

articles/reliability/reliability-bastion.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Azure Bastion supports availability zones in both zone-redundant and zonal confi
4949

5050
The following diagram shows a zone-redundant bastion host, with its instances spread across three zones:
5151

52-
:::image type="content" source="media/bastion/bastion-instances-zones.png" alt-text="Diagram that shows an Azure Bastion bastion host with three instances, each in a separate availability zone." border="false":::
52+
:::image type="content" source="media/reliability-bastion/bastion-instances-zones.png" alt-text="Diagram that shows an Azure Bastion bastion host with three instances, each in a separate availability zone." border="false":::
5353

5454
If you specify more availability zones than you have instances, Azure Bastion spreads instances across as many zones as it can.
5555

@@ -101,7 +101,7 @@ This section describes what to expect when bastion hosts are configured for avai
101101
If you configure zone redundancy on Azure Bastion, a session might be sent to an Azure Bastion instance in an availability zone that's different from the virtual machine you're connecting to. In the following diagram, a request from the user is sent to an Azure Bastion instance in zone 2, although the virtual machine is in zone 1:
102102

103103
<!-- Art Library Source# ConceptArt-0-000-015- -->
104-
:::image type="content" source="./media/bastion/bastion-instance-zone-traffic.png" alt-text="Diagram that shows Azure Bastion with three instances. A user request goes to an Azure Bastion instance in zone 2 and is sent to a VM in zone 1." border="false":::
104+
:::image type="content" source="./media/reliability-bastion/bastion-instance-zone-traffic.png" alt-text="Diagram that shows Azure Bastion with three instances. A user request goes to an Azure Bastion instance in zone 2 and is sent to a VM in zone 1." border="false":::
105105

106106
> [!TIP]
107107
> In most scenarios, the amount of cross-zone latency isn't significant. However, if you have unusually stringent latency requirements your workloads, you should deploy a dedicated single-zone Azure Bastion instance in the virtual machine's availability zone. Keep in mind that this configuration doesn't provide zone redundancy, and we don't recommend it for most customers.

0 commit comments

Comments
 (0)