AWS sagemaker-unified-studio documentation change
Summary
Added documentation for restricted glossary configuration with granular access controls
Security assessment
The change introduces new options for restricting glossary access to specific projects or domain units, enhancing data governance capabilities. While this adds security-related documentation about access controls, there's no evidence it addresses a specific existing security vulnerability.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/create-maintain-business-glossary.md b/sagemaker-unified-studio/latest/userguide/create-maintain-business-glossary.md index cd0db39db..71c8b0e2a 100644 --- a//sagemaker-unified-studio/latest/userguide/create-maintain-business-glossary.md +++ b//sagemaker-unified-studio/latest/userguide/create-maintain-business-glossary.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon SageMaker Unified Studio](/sagemaker/index.html)[User Guide](what-is-sagemaker-unified-studio.html) +[Documentation](/index.html)[Amazon SageMaker Unified Studio](/next-generation-sagemaker/index.html)[User Guide](what-is-sagemaker-unified-studio.html) @@ -19 +19,9 @@ To create a glossary, complete the following steps: - 5. Enable the new glossary by choosing the **Enabled** toggle. + 5. Optional - if you want to create a [restricted glossary](./restricted-asset-classification.html), then choose **Restrict this glossary for governed term use**. And then specify the usage permission by selecting one of the following options: + + * All projects - give permissions to all projects in this domain + + * (Default) Owning project - give permissions ONLY to the owning project + + * Selected projects or domain units - give permission to specific projects and/or domain units + + 6. Enable the new glossary by choosing the **Enabled** toggle.