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/iot-edge/how-to-configure-proxy-support.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
@@ -17,25 +17,25 @@ IoT Edge devices send HTTPS requests to communicate with IoT Hub. If your device
17
17
18
18
This article walks through the following four steps to configure and then manage an IoT Edge device behind a proxy server:
19
19
20
-
1. Install the IoT Edge runtime on your device.
20
+
1.**Install the IoT Edge runtime on your device.**
21
21
22
22
The IoT Edge installation scripts pull packages and files from the internet, so your device needs to communicate through the proxy server to make those requests. For detailed steps, see the [Install the runtime through a proxy](#install-the-runtime-through-a-proxy) section of this article. For Windows devices, the installation script also provides an [Offline installation](how-to-install-iot-edge-windows.md#offline-installation) option.
23
23
24
24
This step is a one-time process performed on the IoT Edge device when you first set it up. The same connections are also required when you update the IoT Edge runtime.
25
25
26
-
2. Configure the Docker daemon and the IoT Edge daemon on your device.
26
+
2.**Configure the Docker daemon and the IoT Edge daemon on your device.**
27
27
28
28
IoT Edge uses two daemons on the device, both of which need to make web requests through the proxy server. The IoT Edge daemon is responsible for communications with IoT Hub. The Moby daemon is responsible for container management, so communicates with container registries. For detailed steps, see the [Configure the daemons](#configure-the-daemons) section of this article.
29
29
30
30
This step is a one-time process performed on the IoT Edge device when you first set it up.
31
31
32
-
3. Configure the IoT Edge agent properties in the config.yaml file on your device.
32
+
3.**Configure the IoT Edge agent properties in the config.yaml file on your device.**
33
33
34
34
The IoT Edge daemon starts the edgeAgent module initially, but then the edgeAgent module is responsible for retrieving the deployment manifest from IoT Hub and starting all the other modules. For the IoT Edge agent to make the initial connection to IoT Hub, configure the edgeAgent module environment variables manually on the device itself. After the initial connection, you can configure the edgeAgent module remotely. For detailed steps, see the [Configure the IoT Edge agent](#configure-the-iot-edge-agent) section of this article.
35
35
36
36
This step is a one-time process performed on the IoT Edge device when you first set it up.
37
37
38
-
4. For all future module deployments, set environment variables for any module communicating through the proxy.
38
+
4.**For all future module deployments, set environment variables for any module communicating through the proxy.**
39
39
40
40
Once your IoT Edge device is set up and connected to IoT Hub through the proxy server, you need to maintain the connection in all future module deployments. For detailed steps, see the [Configure deployment manifests](#configure-deployment-manifests) section of this article.
0 commit comments