AWS sagemaker medium security documentation change
Summary
Added section distinguishing between built-in LCC (admin-controlled, auto-updating) and default LCC (user-selected, persistent)
Security assessment
Clarifies security boundaries: built-in LCC provides centralized control for security patches/enforcement while default LCC maintains user autonomy. Critical for secure environment management.
Diff
diff --git a/sagemaker/latest/dg/studio-lifecycle-configurations.md b/sagemaker/latest/dg/studio-lifecycle-configurations.md index 1ae6ec27c..167369fb6 100644 --- a//sagemaker/latest/dg/studio-lifecycle-configurations.md +++ b//sagemaker/latest/dg/studio-lifecycle-configurations.md @@ -6,0 +7,2 @@ +Understanding built-in and default lifecycle configurations + @@ -36,0 +39,11 @@ Users create and attach built-in lifecycle configurations to their own user prof +## Understanding built-in and default lifecycle configurations + +There are two types of lifecycle configurations in Studio: + + * Built-in LCC: Built-in LCC is controlled by the administrator, always runs when a space starts, and resolves dynamically from the domain settings at launch time. When an administrator updates the built-in LCC at the domain level, all spaces automatically pick up the new LCC on their next launch without requiring any user action. + + * Default LCC: The default LCC is pre-selected for the user at the space level and persists until the user explicitly changes it. Updating the domain-level default LCC does not affect running spaces until they are restarted. + + + +