From 7cd5cc6625ed59ce6dea4eb88110eb7185f2ba76 Mon Sep 17 00:00:00 2001 From: Alfred Gedeon Date: Wed, 23 Aug 2023 10:53:57 -0700 Subject: [PATCH] Doc: fix aws_secret_access env variable --- samples/websocket_connect.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/websocket_connect.md b/samples/websocket_connect.md index d498fca9..38ef539a 100644 --- a/samples/websocket_connect.md +++ b/samples/websocket_connect.md @@ -31,7 +31,7 @@ Replace with the following with the data from your AWS account: Note that in a real application, you may want to avoid the use of wildcards in your ClientID or use them selectively. Please follow best practices when working with AWS on production applications using the SDK. Also, for the purposes of this sample, please make sure your policy allows a client ID of `test-*` to connect or use `--client_id ` to send the client ID your policy supports. -For this sample, using Websockets will attempt to fetch the AWS credentials to authorize the connection from your environment variables or local files. See the [authorizing direct AWS](https://docs.aws.amazon.com/iot/latest/developerguide/authorizing-direct-aws.html) page for documentation on how to get the AWS credentials, which then you can set to the `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS`, and `AWS_SESSION_TOKEN` environment variables. +For this sample, using Websockets will attempt to fetch the AWS credentials to authorize the connection from your environment variables or local files. See the [authorizing direct AWS](https://docs.aws.amazon.com/iot/latest/developerguide/authorizing-direct-aws.html) page for documentation on how to get the AWS credentials, which then you can set to the `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, and `AWS_SESSION_TOKEN` environment variables.