Skip to content

Commit 9569dd0

Browse files
committed
205156 - ms.custom value added | updated
1 parent b7bf3f6 commit 9569dd0

10 files changed

+18
-11
lines changed

articles/iot-edge/iot-edge-as-gateway.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.date: 02/25/2019
88
ms.topic: conceptual
99
ms.service: iot-edge
1010
services: iot-edge
11+
ms.custom: [amqp, mqtt]
1112
---
1213
# How an IoT Edge device can be used as a gateway
1314

articles/iot-edge/iot-edge-certs.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.date: 10/29/2019
88
ms.topic: conceptual
99
ms.service: iot-edge
1010
services: iot-edge
11+
ms.custom: mqtt
1112
---
1213

1314
# Understand how Azure IoT Edge uses certificates

articles/iot-edge/iot-edge-runtime.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.date: 11/01/2019
88
ms.topic: conceptual
99
ms.service: iot-edge
1010
services: iot-edge
11+
ms.custom: [amqp, mqtt]
1112
---
1213

1314
# Understand the Azure IoT Edge runtime and its architecture
@@ -43,7 +44,7 @@ To reduce the bandwidth that your IoT Edge solution uses, the IoT Edge hub optim
4344

4445
![IoT Edge hub is a gateway between physical devices and IoT Hub](./media/iot-edge-runtime/Gateway.png)
4546

46-
IoT Edge hub can determine whether it's connected to IoT Hub. If the connection is lost, IoT Edge hub saves messages or twin updates locally. Once a connection is reestablished, it syncs all the data. The location used for this temporary cache is determined by a property of the IoT Edge hubs module twin. The size of the cache is not capped and will grow as long as the device has storage capacity. For more information, see [Offline capabilities](offline-capabilities.md).
47+
IoT Edge hub can determine whether it's connected to IoT Hub. If the connection is lost, IoT Edge hub saves messages or twin updates locally. Once a connection is reestablished, it syncs all the data. The location used for this temporary cache is determined by a property of the IoT Edge hub's module twin. The size of the cache is not capped and will grow as long as the device has storage capacity. For more information, see [Offline capabilities](offline-capabilities.md).
4748

4849
### Module communication
4950

@@ -77,10 +78,10 @@ The IoT Edge agent is the other module that makes up the Azure IoT Edge runtime.
7778

7879
The [IoT Edge security daemon](iot-edge-security-manager.md) starts the IoT Edge agent on device startup. The agent retrieves its module twin from IoT Hub and inspects the deployment manifest. The deployment manifest is a JSON file that declares the modules that need to be started.
7980

80-
Each item in the deployment manifest contains specific information about a module and is used by the IoT Edge agent for controlling the modules lifecycle. Some of the more interesting properties are:
81+
Each item in the deployment manifest contains specific information about a module and is used by the IoT Edge agent for controlling the module's lifecycle. Some of the more interesting properties are:
8182

8283
* **settings.image** – The container image that the IoT Edge agent uses to start the module. The IoT Edge agent must be configured with credentials for the container registry if the image is protected by a password. Credentials for the container registry can be configured remotely using the deployment manifest, or on the IoT Edge device itself by updating the `config.yaml` file in the IoT Edge program folder.
83-
* **settings.createOptions** – A string that is passed directly to the Moby container daemon when starting a modules container. Adding options in this property allows for advanced configurations like port forwarding or mounting volumes into a modules container.  
84+
* **settings.createOptions** – A string that is passed directly to the Moby container daemon when starting a module's container. Adding options in this property allows for advanced configurations like port forwarding or mounting volumes into a module's container.  
8485
* **status** – The state in which the IoT Edge agent places the module. Usually, this value is set to *running* as most people want the IoT Edge agent to immediately start all modules on the device. However, you could specify the initial state of a module to be stopped and wait for a future time to tell the IoT Edge agent to start a module. The IoT Edge agent reports the status of each module back to the cloud in the reported properties. A difference between the desired property and the reported property is an indicator of a misbehaving device. The supported statuses are:
8586

8687
* Downloading
@@ -114,7 +115,7 @@ For more information, see [Learn how to deploy modules and establish routes in I
114115

115116
### Security
116117

117-
The IoT Edge agent plays a critical role in the security of an IoT Edge device. For example, it performs actions like verifying a modules image before starting it.
118+
The IoT Edge agent plays a critical role in the security of an IoT Edge device. For example, it performs actions like verifying a module's image before starting it.
118119

119120
For more information about the Azure IoT Edge security framework, read about the [IoT Edge security manager](iot-edge-security-manager.md).
120121

articles/iot-edge/production-checklist.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.date: 4/02/2020
88
ms.topic: conceptual
99
ms.service: iot-edge
1010
services: iot-edge
11+
ms.custom: [amqp, mqtt]
1112
---
1213

1314
# Prepare to deploy your IoT Edge solution in production

articles/iot-edge/troubleshoot.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.date: 11/20/2019
88
ms.topic: conceptual
99
ms.service: iot-edge
1010
services: iot-edge
11+
ms.custom: [amqp, mqtt]
1112
---
1213

1314
# Common issues and resolutions for Azure IoT Edge

articles/iot-edge/tutorial-csharp-module-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: kgremban
99
ms.date: 04/23/2019
1010
ms.topic: tutorial
1111
ms.service: iot-edge
12-
ms.custom: mvc
12+
ms.custom: [mvc, amqp]
1313

1414
---
1515

articles/iot-edge/tutorial-java-module.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.author: kgremban
99
ms.date: 04/04/2019
1010
ms.topic: tutorial
1111
ms.service: iot-edge
12-
ms.custom: mvc
12+
ms.custom: [mvc, mqtt]
1313
---
1414

1515
# Tutorial: Develop a Java IoT Edge module for Linux devices

articles/iot-edge/tutorial-machine-learning-edge-05-configure-edge-device.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.date: 2/5/2020
88
ms.topic: tutorial
99
ms.service: iot-edge
1010
services: iot-edge
11+
ms.custom: amqp
1112
---
1213
# Tutorial: Configure an IoT Edge device
1314

@@ -20,7 +21,7 @@ The steps in this article are typically performed by a cloud developer.
2021

2122
## Create certificates
2223

23-
For a device to function as a gateway it needs to be able to securely connect to downstream devices. Azure IoT Edge allows you to use a public key infrastructure (PKI) to set up secure connections between devices. In this case, were allowing a downstream IoT device to connect to an IoT Edge device acting as a transparent gateway. To maintain reasonable security, the downstream device should confirm the identity of the IoT Edge device. For more information about how IoT Edge devices use certificates, see [Azure IoT Edge certificate usage details](iot-edge-certs.md).
24+
For a device to function as a gateway it needs to be able to securely connect to downstream devices. Azure IoT Edge allows you to use a public key infrastructure (PKI) to set up secure connections between devices. In this case, we're allowing a downstream IoT device to connect to an IoT Edge device acting as a transparent gateway. To maintain reasonable security, the downstream device should confirm the identity of the IoT Edge device. For more information about how IoT Edge devices use certificates, see [Azure IoT Edge certificate usage details](iot-edge-certs.md).
2425

2526
In this section, we create the self-signed certificates using a Docker image that we then build and run. We chose to use a Docker image to complete this step because it significantly reduces the number of steps needed to create the certificates on the Windows development machine. See [Create demo certificates to test IoT Edge device features](how-to-create-test-certificates.md) to understand what we automated with the Docker image.
2627

@@ -276,21 +277,21 @@ Next we will update the certificates and hostname by directly editing the config
276277
sudo systemctl restart iotedge
277278
```
278279
279-
7. Check the status of the IoT Edge Daemon (after the command, type “:q” to exit).
280+
7. Check the status of the IoT Edge Daemon (after the command, type ":q" to exit).
280281
281282
```bash
282283
systemctl status iotedge
283284
```
284285
285-
8. If you see errors (colored text prefixed with \[ERROR\]) in the status Examine daemon logs for detailed error information.
286+
8. If you see errors (colored text prefixed with "\[ERROR\]") in the status Examine daemon logs for detailed error information.
286287
287288
```bash
288289
journalctl -u iotedge --no-pager --no-full
289290
```
290291
291292
## Next steps
292293
293-
We just completed configuring an Azure VM as Azure IoT Edge Transparent Gateway. We started by generating test certificates that we uploaded to Azure Key Vault. Next, we used a script and Resource Manager template to deploy the VM with the Ubuntu Server 16.04 LTS + Azure IoT Edge runtime image from the Azure Marketplace. With the VM up and running we connected via SSH, we signed into Azure and downloaded certificates from Key Vault. We made several updates to the configuration of the IoT Edge Runtime by updating the config.yaml file.
294+
We just completed configuring an Azure VM as Azure IoT Edge Transparent Gateway. We started by generating test certificates that we uploaded to Azure Key Vault. Next, we used a script and Resource Manager template to deploy the VM with the "Ubuntu Server 16.04 LTS + Azure IoT Edge runtime" image from the Azure Marketplace. With the VM up and running we connected via SSH, we signed into Azure and downloaded certificates from Key Vault. We made several updates to the configuration of the IoT Edge Runtime by updating the config.yaml file.
294295
295296
For more information see [How an IoT Edge device can be used as a gateway](iot-edge-as-gateway.md) and [Configure an IoT Edge device to act as a transparent gateway](how-to-create-transparent-gateway.md).
296297

articles/iot-fundamentals/iot-introduction.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ services: iot-fundamentals
77
ms.topic: overview
88
ms.date: 01/15/2020
99
ms.author: dobett
10+
ms.custom: [amqp, mqtt]
1011
#Customer intent: As a newcomer to IoT, I want to understand what IoT is, what services are available, and examples of business cases so I can figure out where to start.
1112
---
1213

articles/iot-fundamentals/security-recommendations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ services: iot-hub
88
ms.topic: article
99
ms.date: 11/13/2019
1010
ms.author: dkshir
11-
ms.custom: security-recommendations
11+
ms.custom: [security-recommendations, amqp, mqtt]
1212
---
1313

1414
# Security recommendations for Azure Internet of Things (IoT) deployment

0 commit comments

Comments
 (0)