Skip to content

Conversation

@utezduyar
Copy link

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

Motivation

  • Please give a brief description for the background of this change.
  • Issue number:

Modifications

Change summary

Please describe what changes are included in this pull request.

Revision diff summary

If there is more than one revision, please explain what has been changed since the last revision.

Testing

Is your change tested? If not, please justify the reason.
Please list your testing steps and test results.

  • CI test run result:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

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
@kstribrnAmzn
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants