AWS sagemaker-unified-studio documentation change
Summary
Updated capitalization of 'catalog' to 'Catalog' in multiple sections to reflect proper service naming consistency
Security assessment
Changes are purely capitalization/naming convention updates (e.g., 'SageMaker catalog' to 'SageMaker Catalog'). No security-related content was added or modified. The existing security context around IAM permissions and cross-account access remains unchanged.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/concepts.md b/sagemaker-unified-studio/latest/userguide/concepts.md index b44ed8260..dcfd4bfb0 100644 --- a//sagemaker-unified-studio/latest/userguide/concepts.md +++ b//sagemaker-unified-studio/latest/userguide/concepts.md @@ -51 +51 @@ In Amazon SageMaker Unified Studio, an asset is an entity that presents a single -Asset types define how assets are represented in the Amazon SageMaker catalog. An asset type defines the schema for a specific type of asset. When assets are created, they are validated against the schema defined by their asset type (by default, the latest version). When an asset update occurs, Amazon SageMaker Unified Studio creates a new asset version and enables Amazon SageMaker Unified Studio users to operate on all asset versions. +Asset types define how assets are represented in the Amazon SageMaker Catalog. An asset type defines the schema for a specific type of asset. When assets are created, they are validated against the schema defined by their asset type (by default, the latest version). When an asset update occurs, Amazon SageMaker Unified Studio creates a new asset version and enables Amazon SageMaker Unified Studio users to operate on all asset versions. @@ -56 +56 @@ Asset types define how assets are represented in the Amazon SageMaker catalog. A -Use account associations in Amazon SageMaker Unified Studio to publish data from other AWS accounts into the Amazon SageMaker catalog and create projects to work with data across multiple AWS accounts. AWS accounts where Amazon SageMaker unified root domains are created initiate the account association requests. You can request association from the Amazon SageMaker management console. Account association requests must be accepted by the administrators of the AWS accounts invited for account association. You can authorize the domain account to use data or allow infrastructure deployment with the right IAM permissions as part of approval. Once an associated account is linked to a domain, projects in Amazon SageMaker Unified Studio can use resources from those accounts and also other types of assets. You can deploy resources in specific AWS accounts through project profiles. +Use account associations in Amazon SageMaker Unified Studio to publish data from other AWS accounts into the Amazon SageMaker Catalog and create projects to work with data across multiple AWS accounts. AWS accounts where Amazon SageMaker unified root domains are created initiate the account association requests. You can request association from the Amazon SageMaker management console. Account association requests must be accepted by the administrators of the AWS accounts invited for account association. You can authorize the domain account to use data or allow infrastructure deployment with the right IAM permissions as part of approval. Once an associated account is linked to a domain, projects in Amazon SageMaker Unified Studio can use resources from those accounts and also other types of assets. You can deploy resources in specific AWS accounts through project profiles. @@ -106 +106 @@ In Amazon SageMaker Unified Studio, AWS account owners create roles, policies, a -A blueprint is used to create the project profile that defines which AWS tools and services project members can use as they work with data in the Amazon SageMaker catalog. +A blueprint is used to create the project profile that defines which AWS tools and services project members can use as they work with data in the Amazon SageMaker Catalog. @@ -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. @@ -155 +155 @@ In Amazon SageMaker Unified Studio, you can use data sources to import technical -In Amazon SageMaker Unified Studio, a data source run is a task that Amazon SageMaker Unified Studio performs in order to create assets in project inventories and also optionally to publish project inventory assets to the Amazon SageMaker catalog. Data source runs can be automated (started when a data source is initially created), scheduled, or manual. Use data selection criteria to fine-tune the existing and future data sets to be ingested into project inventories or the Amazon SageMaker catalog and the frequency of metadata updates to those inventory or catalog assets. +In Amazon SageMaker Unified Studio, a data source run is a task that Amazon SageMaker Unified Studio performs in order to create assets in project inventories and also optionally to publish project inventory assets to the Amazon SageMaker Catalog. Data source runs can be automated (started when a data source is initially created), scheduled, or manual. Use data selection criteria to fine-tune the existing and future data sets to be ingested into project inventories or the Amazon SageMaker Catalog and the frequency of metadata updates to those inventory or catalog assets. @@ -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 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. @@ -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 Amazon SageMaker Catalog which is discussed later.