Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update secure-tunnel name #607

Merged
merged 1 commit into from
Aug 2, 2023
Merged

Update secure-tunnel name #607

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions samples/secure_tunneling/secure_tunnel/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Create a new secure tunnel in the AWS IoT console (https://console.aws.amazon.co
To run the sample with a destination access token in destination mode (default), you can use the following command:

``` sh
./secure_tunnel --signing_region <signing_region> --access_token_file <path to destination access token>
./secure-tunnel --signing_region <signing_region> --access_token_file <path to destination access token>
```

The sample will create a Secure Tunnel connection and remain connected in `DESTINATION MODE` and will echo any messages it receives through the Secure Tunnel back to the Source Device.
Expand All @@ -23,7 +23,7 @@ The sample will create a Secure Tunnel connection and remain connected in `DESTI
While the focus of the Secure Tunnel Client for the IoT Device SDK is to connect with Secure Tunnels in `DESTINATION MODE` we also support connecting in `SOURCE MODE`. The token file should be the Source Token in this instance and you must add the `--localProxyModeSource` flag:

``` sh
./secure_tunnel --signing_region <signing_region> --access_token_file <path to source access token> --localProxyModeSource
./secure-tunnel --signing_region <signing_region> --access_token_file <path to source access token> --localProxyModeSource
```

Then two samples will then connect to each other through the AWS Secure Tunnel endpoint and establish a stream through which data can be transmitted in either direction.
Expand Down
Loading