AWS ivs documentation change
Summary
Updated documentation links by adding an extra slash in AWS documentation URLs (formatting correction)
Security assessment
The changes only modify URL paths by adding an extra slash (e.g., '/ivs/' becomes '//ivs/'), which appears to be a formatting correction rather than addressing security issues. No security vulnerabilities, mitigations, or new security features are mentioned in the context of these changes.
Diff
diff --git a/ivs/latest/LowLatencyUserGuide/troubleshooting-faqs.md b/ivs/latest/LowLatencyUserGuide/troubleshooting-faqs.md index 6da8c68c6..14ce3fe24 100644 --- a//ivs/latest/LowLatencyUserGuide/troubleshooting-faqs.md +++ b//ivs/latest/LowLatencyUserGuide/troubleshooting-faqs.md @@ -42 +42 @@ From a viewer's perspective, starvation events may appear as video that lags, bu -To allow monitoring for starvation events, IVS sends starvation events as Amazon EventBridge events; see [Examples: Stream Health Change](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/eventbridge.html#eventbridge-examples-stream-health-change) in _Using Amazon EventBridge with Amazon IVS_. These are sent when a stream enters or exits a state of starvation. Depending on the use case, you can take an appropriate action, like notifying the broadcaster and viewers of intermittent stream conditions. +To allow monitoring for starvation events, IVS sends starvation events as Amazon EventBridge events; see [Examples: Stream Health Change](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/eventbridge.html#eventbridge-examples-stream-health-change) in _Using Amazon EventBridge with Amazon IVS_. These are sent when a stream enters or exits a state of starvation. Depending on the use case, you can take an appropriate action, like notifying the broadcaster and viewers of intermittent stream conditions. @@ -54 +54 @@ Often, stream disconnection aligns with a stream-starvation event; the starvatio - * **IVS StopStream operation** — During an IVS stream session, if the [StopStream](https://docs.aws.amazon.com/ivs/latest/LowLatencyAPIReference/API_StopStream.html) API call is made, the IVS stream session will end. The StopStream operation disconnects the incoming RTMPS stream from the IVS ingest server. Depending on the encoding software/hardware being used, a new stream session may be attempted. + * **IVS StopStream operation** — During an IVS stream session, if the [StopStream](https://docs.aws.amazon.com//ivs/latest/LowLatencyAPIReference/API_StopStream.html) API call is made, the IVS stream session will end. The StopStream operation disconnects the incoming RTMPS stream from the IVS ingest server. Depending on the encoding software/hardware being used, a new stream session may be attempted. @@ -69 +69 @@ To enable faster switching between networks, we recommend that you use the [stre -Redundancy within IVS can be achieved in several ways; see [IVS Resilience](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/security-resilience.html) in _IVS Security_ . +Redundancy within IVS can be achieved in several ways; see [IVS Resilience](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/security-resilience.html) in _IVS Security_ . @@ -80 +80 @@ IVS is separated into different networking planes; Control and Data. -Also see [Global Solution, Regional Control](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/what-is.html#what-is-aws). Consider these two scenarios: +Also see [Global Solution, Regional Control](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/what-is.html#what-is-aws). Consider these two scenarios: @@ -84 +84 @@ Also see [Global Solution, Regional Control](https://docs.aws.amazon.com/ivs/lat -If [playback authorization](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/private-channels-enable-playback-auth.html) is enabled, current viewers probably can continue their playback of ongoing streams, but new viewers may not be able to start viewing if there are issues with playback key-pair authorization. If playback authorization is not enabled, both current and new viewers should be able to view the ongoing stream. +If [playback authorization](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/private-channels-enable-playback-auth.html) is enabled, current viewers probably can continue their playback of ongoing streams, but new viewers may not be able to start viewing if there are issues with playback key-pair authorization. If playback authorization is not enabled, both current and new viewers should be able to view the ongoing stream. @@ -158 +158 @@ We recommend the following methods of monitoring for stream-starvation events: - * [ Amazon EventBridge with Amazon IVS](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/eventbridge.html#eventbridge-examples-stream-health-change) — When a stream-starvation event starts or ends, IVS produces an EventBridge stream health change event. Using Amazon EventBridge targets and rules, you can use these stream-starvation event to get alerts when stream starvation is occurring. For details on targets and rules, see the [Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). + * [ Amazon EventBridge with Amazon IVS](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/eventbridge.html#eventbridge-examples-stream-health-change) — When a stream-starvation event starts or ends, IVS produces an EventBridge stream health change event. Using Amazon EventBridge targets and rules, you can use these stream-starvation event to get alerts when stream starvation is occurring. For details on targets and rules, see the [Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). @@ -162 +162 @@ We recommend the following methods of monitoring for stream-starvation events: - * Filtering Streams by Health — With the IVS console or the IVS [ListStreams](https://docs.aws.amazon.com/ivs/latest/LowLatencyAPIReference/API_ListStreams.html) API operation, you can use the `health` filter to find stream sessions that are in a `STARVING` state. Also, the IVS CloudWatch metric for `ConcurrentStreams` includes a `Health` dimension that you can use to gather a total count of streams that are in a stream-starvation state. See [Monitoring Amazon IVS Low-Latency Streaming](./stream-health.html). + * Filtering Streams by Health — With the IVS console or the IVS [ListStreams](https://docs.aws.amazon.com//ivs/latest/LowLatencyAPIReference/API_ListStreams.html) API operation, you can use the `health` filter to find stream sessions that are in a `STARVING` state. Also, the IVS CloudWatch metric for `ConcurrentStreams` includes a `Health` dimension that you can use to gather a total count of streams that are in a stream-starvation state. See [Monitoring Amazon IVS Low-Latency Streaming](./stream-health.html). @@ -164 +164 @@ We recommend the following methods of monitoring for stream-starvation events: - * You can use the IVS [GetStream](https://docs.aws.amazon.com/ivs/latest/LowLatencyAPIReference/API_GetStream.html) operation to analyze an individual stream. + * You can use the IVS [GetStream](https://docs.aws.amazon.com//ivs/latest/LowLatencyAPIReference/API_GetStream.html) operation to analyze an individual stream. @@ -173 +173 @@ Also see What is stream starvation? -You can use Amazon CloudWatch to proactively monitor/manage IVS service quotas. See [IVS Service Quotas](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/service-quotas.html). This documentation includes information on creating CloudWatch alarms for usage metrics. +You can use Amazon CloudWatch to proactively monitor/manage IVS service quotas. See [IVS Service Quotas](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/service-quotas.html). This documentation includes information on creating CloudWatch alarms for usage metrics. @@ -175 +175 @@ You can use Amazon CloudWatch to proactively monitor/manage IVS service quotas. -We recommend that you set up a proper SNS topic to notify the correct individuals/groups when an alarm is triggered. If the alarm is triggered and the quota is adjustable, you should request a service-quota increase with a new value. See [IVS Service Quotas](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/service-quotas.html) for information on requesting an increase. +We recommend that you set up a proper SNS topic to notify the correct individuals/groups when an alarm is triggered. If the alarm is triggered and the quota is adjustable, you should request a service-quota increase with a new value. See [IVS Service Quotas](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/service-quotas.html) for information on requesting an increase. @@ -314 +314 @@ See if a `recordingConfigurationArn` is returned. - 2. Look in the designated S3 bucket for the Recording Contents for the specific stream session (see [S3 Prefix](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/record-to-s3.html#r2s3-prefix).) The S3 key prefix for a recorded session is in the Amazon EventBridge [Recording State Change event](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/eventbridge.html#eventbridge-examples-recording-state-change). Note: If the [merge fragmented streams](https://docs.aws.amazon.com/ivs/latest/LowLatencyUserGuide/record-to-s3.html#r2s3-merge-fragmented-streams) feature is enabled, some content may be another recorded session. + 2. Look in the designated S3 bucket for the Recording Contents for the specific stream session (see [S3 Prefix](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/record-to-s3.html#r2s3-prefix).) The S3 key prefix for a recorded session is in the Amazon EventBridge [Recording State Change event](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/eventbridge.html#eventbridge-examples-recording-state-change). Note: If the [merge fragmented streams](https://docs.aws.amazon.com//ivs/latest/LowLatencyUserGuide/record-to-s3.html#r2s3-merge-fragmented-streams) feature is enabled, some content may be another recorded session.