From c7acca7900035be132664ab22661c8ec2b8c71b2 Mon Sep 17 00:00:00 2001 From: Umut Tezduyar Lindskog Date: Wed, 26 Nov 2025 14:19:52 +0100 Subject: [PATCH] Modify local proxy command in README Updated instructions for starting the local proxy to include the new '--destination-client-type V1' option. As of 3.1.2 May 2024 Update, --destination-client-type V1 will be a required parameter when connecting with the following: AWS IoT Device Client AWS IoT Secure Tunneling Component OR Greengrass V2 Secure Tunneling Component Browser-based Secure Tunneling from the AWS Console Any Secure Tunneling demo code written before 2022 1.x versions of the localproxy --- source/tunneling/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/tunneling/README.md b/source/tunneling/README.md index 57fc99320..a0bdc1bad 100644 --- a/source/tunneling/README.md +++ b/source/tunneling/README.md @@ -49,7 +49,7 @@ On your laptop: 2. Copy the source access token 3. Start the [local proxy](https://github.com/aws-samples/aws-iot-securetunneling-localproxy/blob/master/README.md#options-set-via-command-line-arguments) with the source access token. For example: ``` -$ ./localproxy -r us-east-1 -s 8080 -t +$ ./localproxy -r us-east-1 -s 8080 --destination-client-type V1 -t ``` 4. Start the SSH client but connect to the local proxy listening port. For example: ``` @@ -93,4 +93,4 @@ The example policy below demonstrates the minimum permissions required to run th ### Limitation The Secure Tunneling feature within the AWS IoT Device Client currently does not support [multiplex data streams](https://docs.aws.amazon.com/iot/latest/developerguide/multiplexing.html). However the feature supports multiple tunnels each with a single data streams. -[*Back To The Top*](#) \ No newline at end of file +[*Back To The Top*](#)