AWS kinesisvideostreams-webrtc-dg documentation change
Summary
Updated documentation URLs by adding double slashes after the domain in multiple API references and IAM credential links
Security assessment
Changes only modify URL formatting (adding '//' after domain) without altering security-related content. The session token guidance remains unchanged, and no vulnerabilities or security features are addressed.
Diff
diff --git a/kinesisvideostreams-webrtc-dg/latest/devguide/ingest-media.md b/kinesisvideostreams-webrtc-dg/latest/devguide/ingest-media.md index fdd909590..ba308d8e6 100644 --- a//kinesisvideostreams-webrtc-dg/latest/devguide/ingest-media.md +++ b//kinesisvideostreams-webrtc-dg/latest/devguide/ingest-media.md @@ -51 +51 @@ Complete the following fields: - * **Session Token** \- The sample application supports both temporary and long-term credentials. Leave this field blank if you're using long-term IAM credentials. See [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) for more information. + * **Session Token** \- The sample application supports both temporary and long-term credentials. Leave this field blank if you're using long-term IAM credentials. See [Temporary security credentials in IAM](https://docs.aws.amazon.com//IAM/latest/UserGuide/id_credentials_temp.html) for more information. @@ -57 +57 @@ Complete the following fields: - * **WebRTC Ingestion and Storage** \- Expand the node and select **Automatically determine ingestion mode**. This option makes the sample application call the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API to determine in which mode to run. + * **WebRTC Ingestion and Storage** \- Expand the node and select **Automatically determine ingestion mode**. This option makes the sample application call the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API to determine in which mode to run. @@ -61 +61 @@ Complete the following fields: -If the signaling channel is configured for ingestion using the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API, the sample application will automatically invoke the [JoinStorageSession](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_webrtc_JoinStorageSession.html) API immediately after connecting to the Signaling channel to start the WebRTC ingestion workflow. +If the signaling channel is configured for ingestion using the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API, the sample application will automatically invoke the [JoinStorageSession](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_webrtc_JoinStorageSession.html) API immediately after connecting to the Signaling channel to start the WebRTC ingestion workflow. @@ -101 +101 @@ This starts WebRTC ingestion. -Your supplied signaling channel must be configured for storage. Use the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API to confirm. +Your supplied signaling channel must be configured for storage. Use the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API to confirm. @@ -140 +140 @@ Complete the following fields: - * **Session Token** \- The sample application supports both temporary and long-term credentials. Leave this field blank if you're using long-term IAM credentials. See [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) for more information. + * **Session Token** \- The sample application supports both temporary and long-term credentials. Leave this field blank if you're using long-term IAM credentials. See [Temporary security credentials in IAM](https://docs.aws.amazon.com//IAM/latest/UserGuide/id_credentials_temp.html) for more information. @@ -146 +146 @@ Complete the following fields: - * **WebRTC Ingestion and Storage** \- Expand the node and select **Automatically determine ingestion mode**. This option makes the sample application call the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API to determine in which mode to run. + * **WebRTC Ingestion and Storage** \- Expand the node and select **Automatically determine ingestion mode**. This option makes the sample application call the [DescribeMediaStorageConfiguration](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_DescribeMediaStorageConfiguration.html) API to determine in which mode to run. @@ -150 +150 @@ Complete the following fields: -The application automatically calls the [JoinStorageSessionAsViewer](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_webrtc_JoinStorageSessionAsViewer.html) API immediately after connecting to the signaling channel to trigger an SDP offer send to the viewer from the session. +The application automatically calls the [JoinStorageSessionAsViewer](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_webrtc_JoinStorageSessionAsViewer.html) API immediately after connecting to the signaling channel to trigger an SDP offer send to the viewer from the session. @@ -157 +157 @@ The application automatically calls the [JoinStorageSessionAsViewer](https://doc -With peer-to-peer WebRTC, the viewer participant is the controlling peer and the master participant is the controlled peer. In WebRTC ingestion mode, the storage session is now the controlling peer. After connecting to signaling and invoking [JoinStorageSessionAsViewer](https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/API_webrtc_JoinStorageSessionAsViewer.html), the viewer will need to respond to the SDP offer and establish a connection to the storage session through WebRTC. +With peer-to-peer WebRTC, the viewer participant is the controlling peer and the master participant is the controlled peer. In WebRTC ingestion mode, the storage session is now the controlling peer. After connecting to signaling and invoking [JoinStorageSessionAsViewer](https://docs.aws.amazon.com//kinesisvideostreams/latest/dg/API_webrtc_JoinStorageSessionAsViewer.html), the viewer will need to respond to the SDP offer and establish a connection to the storage session through WebRTC.