Skip to content

Latest commit

 

History

History
96 lines (80 loc) · 4.85 KB

README.md

File metadata and controls

96 lines (80 loc) · 4.85 KB
Raw

Secure Tunneling

Notice: Running the AWS IoT Device Client will incur usage of AWS IoT services, and is likely to incur charges on your AWS account. Please refer the pricing pages for AWS IoT Core, AWS IoT Device Management, and AWS IoT Device Defender for more details.

Back To The Main Readme

Secure Tunneling Feature

The Secure Tunneling feature allows you to gain access to a remote device even if the device is behind a firewall. You may want to remote access to a device to troubleshoot, or update its configuration. For complete reference of Secure Tunneling, please see here.

Without the Device Client, if you wanted secure privileged access to a device by secure tunneling, you would need to build and deploy a compatible binary of local proxy onto the device. You'd also need to write, build and deploy code that subscribes to the MQTT new tunnel topic and launches the local proxy. When you use the Device Client, you can skip building the local proxy for your IoT device and writing code to subscribe to the relevant MQTT topics. You can simply build and deploy the Device Client to your IoT devices and enable the Secure Tunneling feature.

Secure Tunneling Feature Configuration Options

You can enable or disable the Secure Tunneling feature by a CLI argument or in the configuration file.

enabled: Whether or not the Secure Tunneling feature is enabled (True/False). If not specified, Secure Tunneling feature is enabled by default.

Configuring the Secure Tunneling feature via the command line

$ ./aws-iot-device-client --enable-tunneling [true|false]

Configuring the Secure Tunneling feature via the JSON configuration file

{
  ...
  "tunneling": {
    "enabled": [true|false]
  }
  ...
}

Example steps to use the Secure Tunneling feature

Here is a sample workflow to access a remote device using the Secure Tunneling feature.

On the remote device:

  1. Deploy and run the Device Client with Secure Tunneling feature enabled

On your laptop:

  1. Create a new secure tunnel on the AWS Console
  2. Copy the source access token
  3. Start the local proxy with the source access token. For example:
$ ./localproxy -r us-east-1 -s 8080 -t <source token>
  1. Start the SSH client but connect to the local proxy listening port. For example:
$ ssh -p 8080 <remote_user_name>@localhost

Policy Permissions

In order to use the Secure Tunneling feature the device must first have permission to connect to IoT Core. The device must also be able to subscribe to and receive messages on the Secure Tunneling notify topic in order to receive the destination token. The example policy below demonstrates the minimum permissions required to run the Secure Tunneling feature. Simply replace the <region> and <accountId> with the correct values.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "iot:Connect",
      "Resource": [
      "arn:aws:iot:<region>:<accountId>:client/${iot:Connection.Thing.ThingName}"
      ]
    },

    {
      "Effect": "Allow",
      "Action": "iot:Subscribe",
      "Resource": [
      "arn:aws:iot:<region>:<accountId>:topicfilter/$aws/things/${iot:Connection.Thing.ThingName}/tunnels/notify"
      ]
    },
    {
      "Effect": "Allow",
      "Action": "iot:Receive",
      "Resource": [
      "arn:aws:iot:<region>:<accountId>:topic/$aws/things/${iot:Connection.Thing.ThingName}/tunnels/notify"
      ]
    }
  ]
}

Limitation

The Secure Tunneling feature within the AWS IoT Device Client currently does not support multiplex data streams. However the feature supports multiple tunnels each with a single data streams.

Back To The Top