Amazon SageMaker Catalog now supports metadata enforcement rules for glossary terms, requiring data producers to apply approved business vocabulary when publishing assets. This helps consistent data classification and improves discoverability across organizational catalogs.
This new capability allows administrators to define mandatory glossary term requirements for data assets during the publishing workflow. Data producers must now classify their assets with approved business terms from organizational glossaries before publication, ensuring consistent metadata standards and improving data discoverability. The enforcement rules validate that required glossary terms are applied, preventing assets from being published without proper business context. By standardizing metadata and aligning technical data schemas with business language, this capability enhances data governance, improves search relevance, and helps business users more easily understand and trust published data assets.
Metadata enforcement rules for glossary terms are available in all AWS regions where Amazon SageMaker Catalog operates.
To get started, visit the Amazon SageMaker console and navigate to the Catalog governance section to configure glossary term enforcement policies. You can also use the AWS CLI or SDKs to programmatically manage metadata rules for asset publishing.
To learn more about Amazon SageMaker Catalog, visit the Amazon Sagemaker documentation.
Categories: marketing:marchitecture/analytics,general:products/amazon-sagemaker
Source: Amazon Web Services
Latest Posts
- Microsoft Purview eDiscovery | Direct export expiration change [MC1217141]
![Microsoft Purview eDiscovery | Direct export expiration change [MC1217141] 2 pexels frank cone 140140 3573555](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Data Security Posture Agent is now available in preview [MC1217155]
![Data Security Posture Agent is now available in preview [MC1217155] 3 glacier 1868192 1920](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Tenant setting update: Copilot capacity designation enabled by default [MC1217152]
![Tenant setting update: Copilot capacity designation enabled by default [MC1217152] 4 pexels jeswin 700971](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Power Pages – Power Pages version 9.8.1.x Pre-Production Release [MC1217124]
![Power Pages - Power Pages version 9.8.1.x Pre-Production Release [MC1217124] 5 pexels foysal ahmed 2102283 6053289](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)

![Microsoft Purview eDiscovery | Direct export expiration change [MC1217141] 2 pexels frank cone 140140 3573555](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-frank-cone-140140-3573555-150x150.webp)
![Data Security Posture Agent is now available in preview [MC1217155] 3 glacier 1868192 1920](https://mwpro.co.uk/wp-content/uploads/2025/06/glacier-1868192_1920-150x150.webp)
![Tenant setting update: Copilot capacity designation enabled by default [MC1217152] 4 pexels jeswin 700971](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-jeswin-700971-150x150.webp)
![Power Pages - Power Pages version 9.8.1.x Pre-Production Release [MC1217124] 5 pexels foysal ahmed 2102283 6053289](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-foysal-ahmed-2102283-6053289-150x150.webp)
