Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Commit

Permalink
Fix issue #67
Browse files Browse the repository at this point in the history
  • Loading branch information
bobwatso-aws committed Mar 25, 2022
1 parent cdcb32e commit a4a362f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions developerguide/iot-rule-sql-version.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@ The following JSON example shows you how to specify the SQL version using the `a
```

AWS IoT currently supports the following SQL versions:
+ `2016-03-23` – The SQL version built on 2016\-03\-23 \(recommended\)\.
+ `2015-10-08` – The original SQL version built on 2015\-10\-08\.
+ `2016-03-23` – The SQL version built on 2016\-03\-23\.
+ `beta` – The most recent beta SQL version\. If you use this version, it might introduce breaking changes to your rules\.
+ `beta` – The most recent beta SQL version\. This version could introduce breaking changes to your rules\.

## What's new in the 2016\-03\-23 SQL rules engine version<a name="sql-2016-03-23-beta"></a>
+ Fixes for selecting nested JSON objects\.
Expand Down
2 changes: 1 addition & 1 deletion developerguide/secure-tunneling.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# AWS IoT secure tunneling<a name="secure-tunneling"></a>

When devices are deployed behind restricted firewalls at remote sites, you need a way to gain access to those devices for troubleshooting, configuration updates, and other operational tasks\. Use secure tunneling to establish bidirectional communication to remote devices over a secure connection that is managed by AWS IoT\. secure tunneling does not require updates to your existing inbound firewall rule, so you can keep the same security level provided by firewall rules at a remote site\.
When devices are deployed behind restricted firewalls at remote sites, you need a way to gain access to those devices for troubleshooting, configuration updates, and other operational tasks\. Use secure tunneling to establish bidirectional communication to remote devices over a secure connection that is managed by AWS IoT\. Secure tunneling does not require updates to your existing inbound firewall rules, so you can keep the same security level provided by firewall rules at a remote site\.

For example, a sensor device located at a factory that is a couple hundred miles away is having trouble measuring the factory temperature\. You can use secure tunneling to open and quickly start a session to that sensor device\. After you have identified the problem \(for example, a bad configuration file\), you can reset the file and restart the sensor device through the same session\. Compared to a more traditional troubleshooting \(for example, sending a technician to the factory to investigate the sensor device\), secure tunneling decreases incident response and recovery time and operational costs\.

0 comments on commit a4a362f

Please sign in to comment.