AWS sagemaker-unified-studio documentation change
Summary
Capitalization changes from 'catalog' to 'Catalog' for consistency, minor terminology adjustments (e.g., 'domain catalog' to 'catalog domain'), and replacement of 'Amazon SageMaker catalog' with 'business data catalog' in one instance.
Security assessment
Changes are primarily capitalization fixes and terminology clarifications. No explicit security vulnerabilities, incident mitigations, or new security features are introduced. References to existing security controls (e.g., permissions for catalog access) remain unchanged in substance.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/concepts.md b/sagemaker-unified-studio/latest/userguide/concepts.md index b44ed8260..f5390bc00 100644 --- a/sagemaker-unified-studio/latest/userguide/concepts.md +++ b/sagemaker-unified-studio/latest/userguide/concepts.md @@ -130 +130 @@ Workflows | Provides an AWS CloudFormation template to create the MWAA environme -**Amazon SageMaker catalog** +**Amazon SageMaker Catalog** @@ -133 +133 @@ Workflows | Provides an AWS CloudFormation template to create the MWAA environme -This is a catalog of all the published assets from various projects. The scope of the Amazon SageMaker catalog is the domain, therefore published assets are discoverable by all projects in that domain. The Amazon SageMaker catalog enables discovery that crosses the account and Region boundary. You can publish assets to the Amazon SageMaker catalogso that other projects can subscribe to them, or you can subscribe to assets in the catalog that were published from other projects. Every asset that lives in the Amazon SageMaker catalog has an owner project (also known as the producer project) which controls policies around how subscriptions can be fulfilled. A subscriber (also known as a consumer project) can make a request to the owner project to gain access to the asset. Once the request is approved, the owner project provides the necessary permissions to the subscriber project so that it may gain access to that asset. +This is a catalog of all the published assets from various projects. The scope of the Amazon SageMaker Catalog is the domain, therefore published assets are discoverable by all projects in that domain. The Amazon SageMaker Catalog enables discovery that crosses the account and Region boundary. You can publish assets to the Amazon SageMaker Catalogso that other projects can subscribe to them, or you can subscribe to assets in the catalog that were published from other projects. Every asset that lives in the Amazon SageMaker Catalog has an owner project (also known as the producer project) which controls policies around how subscriptions can be fulfilled. A subscriber (also known as a consumer project) can make a request to the owner project to gain access to the asset. Once the request is approved, the owner project provides the necessary permissions to the subscriber project so that it may gain access to that asset. @@ -172 +172 @@ In Amazon SageMaker Unified Studio, an IAM principal who creates an Amazon SageM -Use domain units to organize your assets and other domain entities under specific business units and teams. To set up secure and efficient data sharing within and across business units of your organization, you can create domain units within Amazon SageMaker Unified Studio and grant access to selected users within each business unit to log in and share their assets to the Amazon SageMaker catalog. Domain units can also be used for resource owners, such as AWS account owners, to set up Amazon SageMaker Unified Studio authorization permissions on their resources. Domain units provide a delegated authority from account owners to domain unit owners and they can set up authorization permissions on behalf of account owners. +Use domain units to organize your assets and other domain entities under specific business units and teams. To set up secure and efficient data sharing within and across business units of your organization, you can create domain units within Amazon SageMaker Unified Studio and grant access to selected users within each business unit to log in and share their assets to the catalog. Domain units can also be used for resource owners, such as AWS account owners, to set up Amazon SageMaker Unified Studio authorization permissions on their resources. Domain units provide a delegated authority from account owners to domain unit owners and they can set up authorization permissions on behalf of account owners. @@ -187 +187 @@ A metadata form type is a template that defines the metadata that is collected a -In Amazon SageMaker Unified Studio, metadata forms define the metadata that is collected and saved when assets are created as inventory or published in an Amazon SageMaker unified domain. Metadata form definitions are created in the domain catalog by a domain administrator. A metadata form definition is composed of one or more field definitions, with support for boolean, date, decimal, integer, string, and business glossary field value data types. A domain administrator applies a metadata form to assets in their domain by adding the metadata form to their domain. Asset publishers then provide any optional and required field values in the metadata form. +In Amazon SageMaker Unified Studio, metadata forms define the metadata that is collected and saved when assets are created as inventory or published in an Amazon SageMaker unified domain. Metadata form definitions are created in the catalog domain by a domain administrator. A metadata form definition is composed of one or more field definitions, with support for boolean, date, decimal, integer, string, and business glossary field value data types. A domain administrator applies a metadata form to assets in their domain by adding the metadata form to their domain. Asset publishers then provide any optional and required field values in the metadata form. @@ -223 +223 @@ A project exists within a domain. A single Amazon SageMaker unified domain can h -Each project is created using a template called a project profile, which is enabled by an administrator during the setup phase. A project profile controls the tools available within the project. Project members can request access to assets from the Amazon SageMaker catalog and produce new artifacts using one or more of the tools available inside the project. Artifacts in a project are not accessible outside of the project unless they are published to the Amazon SageMaker catalog which is discussed later. +Each project is created using a template called a project profile, which is enabled by an administrator during the setup phase. A project profile controls the tools available within the project. Project members can request access to assets from the Amazon SageMaker Catalog and produce new artifacts using one or more of the tools available inside the project. Artifacts in a project are not accessible outside of the project unless they are published to the business data catalog which is discussed later.