AWS ivs documentation change
Summary
Fixed documentation URLs by adding double slash in paths to AWS API references and guides.
Security assessment
Changes are purely URL formatting corrections with no security context. The updates fix hyperlink paths but do not alter security-related content or address vulnerabilities.
Diff
diff --git a/ivs/latest/RealTimeUserGuide/rt-individual-participant-recording.md b/ivs/latest/RealTimeUserGuide/rt-individual-participant-recording.md index d0f64443e..68cfc7aed 100644 --- a//ivs/latest/RealTimeUserGuide/rt-individual-participant-recording.md +++ b//ivs/latest/RealTimeUserGuide/rt-individual-participant-recording.md @@ -42 +42 @@ For details, see the S3 documentation on [controlling ownership of objects](http -After creating a bucket, call the IVS real-time streaming API to [create a StorageConfiguration](https://docs.aws.amazon.com/ivs/latest/RealTimeAPIReference/API_CreateStorageConfiguration.html) object. Once the storage configuration is successfully created, IVS will have permission to write to the provided S3 bucket. You can re-use this StorageConfiguration object on multiple stages. +After creating a bucket, call the IVS real-time streaming API to [create a StorageConfiguration](https://docs.aws.amazon.com//ivs/latest/RealTimeAPIReference/API_CreateStorageConfiguration.html) object. Once the storage configuration is successfully created, IVS will have permission to write to the provided S3 bucket. You can re-use this StorageConfiguration object on multiple stages. @@ -46 +46 @@ After creating a bucket, call the IVS real-time streaming API to [create a Stora -Now you need to [create an IVS stage](https://docs.aws.amazon.com/ivs/latest/RealTimeAPIReference/API_CreateStage.html) with individual participant recording enabled (by setting the AutoParticipantRecordingConfiguration object), as well as participant tokens for each publisher. +Now you need to [create an IVS stage](https://docs.aws.amazon.com//ivs/latest/RealTimeAPIReference/API_CreateStage.html) with individual participant recording enabled (by setting the AutoParticipantRecordingConfiguration object), as well as participant tokens for each publisher. @@ -81 +81 @@ The request below creates a stage with two participant tokens and individual par -Distribute the participant tokens to your publishers, and have them join the stage and start [publishing to it](https://docs.aws.amazon.com/ivs/latest/RealTimeUserGuide/getting-started-pub-sub.html). +Distribute the participant tokens to your publishers, and have them join the stage and start [publishing to it](https://docs.aws.amazon.com//ivs/latest/RealTimeUserGuide/getting-started-pub-sub.html). @@ -83 +83 @@ Distribute the participant tokens to your publishers, and have them join the sta -When they join the stage and start publishing to it using one of [IVS real-time streaming broadcast SDKs](https://docs.aws.amazon.com/ivs/latest/RealTimeUserGuide/broadcast.html), the participant-recording process starts automatically and sends you an [EventBridge event](./eventbridge.html) indicating that the recording started. (The event is IVS Participant Recording State Change - Recording Start.) Concurrently, the participant-recording process starts writing the VOD and metadata files to the configured S3 bucket. Note: Participants connected for extremely short durations (less than 5s) are not guaranteed to be recorded. +When they join the stage and start publishing to it using one of [IVS real-time streaming broadcast SDKs](https://docs.aws.amazon.com//ivs/latest/RealTimeUserGuide/broadcast.html), the participant-recording process starts automatically and sends you an [EventBridge event](./eventbridge.html) indicating that the recording started. (The event is IVS Participant Recording State Change - Recording Start.) Concurrently, the participant-recording process starts writing the VOD and metadata files to the configured S3 bucket. Note: Participants connected for extremely short durations (less than 5s) are not guaranteed to be recorded. @@ -107 +107 @@ There are two ways to get the S3 prefix for each recording: - * Use the [GetParticipant](https://docs.aws.amazon.com/ivs/latest/RealTimeAPIReference/API_GetParticipant.html) API operation — The response includes the S3 bucket and prefix to where a participant is being recorded. Here is the request: + * Use the [GetParticipant](https://docs.aws.amazon.com//ivs/latest/RealTimeAPIReference/API_GetParticipant.html) API operation — The response includes the S3 bucket and prefix to where a participant is being recorded. Here is the request: @@ -135 +135 @@ And here is the response: -After the recording is finalized, you can watch it using the [IVS player](https://debug.ivsdemos.com/?p=ivs). See [Playback of Recorded Content from Private Buckets](https://docs.aws.amazon.com/ivs/latest/RealTimeUserGuide/rt-composite-recording.html#comp-rec-playback) for instructions on setting up CloudFront distributions for VOD playback. +After the recording is finalized, you can watch it using the [IVS player](https://debug.ivsdemos.com/?p=ivs). See [Playback of Recorded Content from Private Buckets](https://docs.aws.amazon.com//ivs/latest/RealTimeUserGuide/rt-composite-recording.html#comp-rec-playback) for instructions on setting up CloudFront distributions for VOD playback.