AWS ivs documentation change
Summary
Added documentation about participant recording merge behavior when reconnecting
Security assessment
Documents recording continuity features that help maintain data integrity, which supports security-related auditing capabilities.
Diff
diff --git a/ivs/latest/RealTimeAPIReference/API_Participant.md index ff245f7d8..106f1a515 100644 --- a/ivs/latest/RealTimeAPIReference/API_Participant.md +++ b/ivs/latest/RealTimeAPIReference/API_Participant.md @@ -145 +145 @@ Required: No -S3 prefix of the S3 bucket where the participant is being recorded, if individual participant recording is enabled, or `""` (empty string), if recording is not enabled. +S3 prefix of the S3 bucket where the participant is being recorded, if individual participant recording is enabled, or `""` (empty string), if recording is not enabled. If individual participant recording merge is enabled, and if a stage publisher disconnects from a stage and then reconnects, IVS tries to record to the same S3 prefix as the previous session. See [ Merge Fragmented Individual Participant Recordings](/ivs/latest/RealTimeUserGuide/rt-individual-participant-recording.html#ind-part-rec-merge-frag).