You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
boundary/website/content/docs/concepts/domain-model/session-recordings.mdx

66 lines
2.7 KiB

---
layout: docs
page_title: Domain Model - Session Recordings
description: |-
The anatomy of a Boundary session recording
---
# Session recordings <sup>HCP/ENT</sup>
A session recording represents a directory structure of
files in an external object store that together are the
recording of a single [session][] between a [user][] and a [target][].
The lifecycle of a session recording does not affect the
lifecycle of any files stored in the external object store.
A session recording belongs to one and only one [storage bucket][].
It is deleted when you delete the [storage bucket][] it belongs to.
A session recording is associated with the
[target][] that the recorded session was against.
However, the lifecycle of a session recording is not tied to
the lifecycle of the [target][] it is associated with.
If the [target][] associated wtih a session recording is deleted,
the association to the [target][] is deleted, not the session recording itself.
Deleting a session recording does not delete or modify
any of the files in the external object store that the session recording represents.
The session recording captures all interactions that take place during
the session, including metadata about the [user][], [target][] and any
[hosts][], [host sets][], [host catalogs][], or [credentials][] used.
A session recording represents [connections][] as separate
entities within the recording. Each recorded connection may also contain a recorded channel. This represents a single channel
in which the [user][] interacted with the [target][] in protocols that
multiplex user interactions over single connections. For example,
the SSH protocol multiplexes user interactions in a single
connection, so a user's interactions over SSH are recorded
in a channel.
A session recording belongs to the scope of the [storage bucket][]
it is stored in. The scope can be either the global scope or an [organization][]
scope.
## Referenced by
- [Storage Bucket][]
## Service API Docs
The following services are relevant to this resource:
- [Session recording service](/boundary/api-docs/session-recording-service)
[connections]: /boundary/docs/concepts/domain-model/session-connections
[credentials]: /boundary/docs/concepts/domain-model/credentials
[host catalogs]: /boundary/docs/concepts/domain-model/host-catalogs
[host sets]: /boundary/docs/concepts/domain-model/host-sets
[hosts]: /boundary/docs/concepts/domain-model/hosts
[target]: /boundary/docs/concepts/domain-model/targets
[user]: /boundary/docs/concepts/domain-model/users
[organization]: /boundary/docs/concepts/domain-model/scopes#organizations
[session]: /boundary/docs/concepts/domain-model/sessions
[storage bucket]: /boundary/docs/concepts/domain-model/storage-buckets