AWS kinesisvideostreams documentation change
Summary
Updated documentation link to include double slashes in URL for consistency
Security assessment
The change is purely a URL formatting adjustment. While the surrounding content discusses X.509 certificate authentication, the diff itself does not introduce or modify security-related documentation or address a security issue.
Diff
diff --git a/kinesisvideostreams/latest/dg/how-iot.md b/kinesisvideostreams/latest/dg/how-iot.md index 9629b1aa7..bb2021c04 100644 --- a//kinesisvideostreams/latest/dg/how-iot.md +++ b//kinesisvideostreams/latest/dg/how-iot.md @@ -13 +13 @@ Devices can use X.509 certificates to connect to AWS IoT using TLS mutual authen -The credentials provider authenticates a client (in this case, a Kinesis Video Streams SDK that's running on the camera that you want to send data to a video stream) using an X.509 certificate and issues a temporary, limited-privilege security token. You can use the token to sign and authenticate any AWS request (in this case, a call to the Kinesis Video Streams). For more information, see [Authorizing Direct Calls to AWS Services](https://docs.aws.amazon.com/iot/latest/developerguide/authorizing-direct-aws.html). +The credentials provider authenticates a client (in this case, a Kinesis Video Streams SDK that's running on the camera that you want to send data to a video stream) using an X.509 certificate and issues a temporary, limited-privilege security token. You can use the token to sign and authenticate any AWS request (in this case, a call to the Kinesis Video Streams). For more information, see [Authorizing Direct Calls to AWS Services](https://docs.aws.amazon.com//iot/latest/developerguide/authorizing-direct-aws.html).