You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-nat-gateway.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Setting up a [container group](container-instances-container-groups.md) with an
15
15
16
16
This article provides steps to configure a container group in a [virtual network](container-instances-virtual-network-concepts.md) integrated with a [Network Address Translation (NAT) gateway](../virtual-network/nat-gateway/nat-overview.md). By configuring a NAT gateway to SNAT a subnet address range delegated to Azure Container Instances (ACI), you can identify outbound traffic from your container groups. The container group egress traffic will use the public IP address of the NAT gateway. A single NAT gateway can be used by multiple container groups deployed in the virtual network's subnet delegated to ACI.
17
17
18
-
In this article you use the Azure CLI to create the resources for this scenario:
18
+
In this article, you use the Azure CLI to create the resources for this scenario:
19
19
20
20
* Container groups deployed on a delegated subnet [in the virtual network](container-instances-vnet.md)
21
21
* A NAT gateway deployed in the network with a static public IP address
@@ -35,7 +35,7 @@ You then validate egress from example container groups through the NAT gateway.
This tutorial will make use of this randomized variable value going forward. If you are using an existing resource group, modify this value of this variable.
38
+
This tutorial makes use of this randomized variable value going forward. If you are using an existing resource group, modify the value of this variable appropriately.
39
39
40
40
**Azure resource group**: If you don't have an Azure resource group already, create a resource group with the [az group create][az-group-create] command.
41
41
@@ -62,7 +62,7 @@ First, use the [az network vnet public-ip create][az-network-public-ip-create] t
@@ -80,7 +80,7 @@ We'll configure the source subnet **aci-subnet** to use a specific NAT gateway r
80
80
81
81
## Test egress from a container group
82
82
83
-
Test inbound access to the *appcontainer* running in the virtual network by browsing to the firewall's public IP address. Previously, you stored the public IP address in variable $NG_PUBLIC_IP
83
+
Test inbound access to the `appcontainer` running in the virtual network by browsing to the firewall's public IP address. Previously, you stored the public IP address in variable $NG_PUBLIC_IP
84
84
85
85
Deploy the following sample container into the virtual network. When it runs, it sends a single HTTP request to `http://checkip.dyndns.org`, which displays the IP address of the sender (the egress IP address). If the application rule on the firewall is configured properly, the firewall's public IP address is returned.
0 commit comments