AWS datazone documentation change
Summary
Updated metadata rule creation steps with more detailed instructions including required form selection, action type, scope configuration, and cascading behavior
Security assessment
Changes focus on improving procedural clarity for metadata rule configuration without mentioning security controls, vulnerabilities, or protections
Diff
diff --git a/datazone/latest/userguide/metadata-rules.md b/datazone/latest/userguide/metadata-rules.md index 0ed409518..6b50eb0df 100644 --- a/datazone/latest/userguide/metadata-rules.md +++ b/datazone/latest/userguide/metadata-rules.md @@ -15 +15 @@ Domain unit owners can can complete the following procedure to configure metadat - 2. Choose **View domains** , navigate to the **Domain units** tab and choose the domain unit that you want to work with. + 2. Choose **Domains** , navigate to the **Domain units** tab and choose the domain unit that you want to work with. @@ -19 +19 @@ Domain unit owners can can complete the following procedure to configure metadat - 4. In the **Name** field, provide the name for the metadata form rule. + 4. On the **Create required metadata form rule** page, do the following and then choose **Add rule** : @@ -21 +21 @@ Domain unit owners can can complete the following procedure to configure metadat - 5. Choose **Add metadata form** , then choose a metadata form within the domain / domain unit that you want to add to this rule, and then choose **Add**. You can add more than one metadata form. + * Specify a name for your rule. @@ -23 +23 @@ Domain unit owners can can complete the following procedure to configure metadat - 6. For rule scope, specify whether the rule applies across all asset types or limit it to specific asset types. Also, choose whether the rule applies to a specific project or all projects within the domain. Once the scope is defined, choose **Add Rule**. + * Under **Action** , choose **Subscription request**. @@ -25 +25 @@ Domain unit owners can can complete the following procedure to configure metadat -###### Note + * Under **Required forms** , choose **Add metadata form** , choose a metadata form within the domain / domain unit that you want to add to this rule, and then choose **Add**. You can add up to 5 metadata forms per rule. @@ -27 +27,5 @@ Domain unit owners can can complete the following procedure to configure metadat -While defining the rule scope, if you choose to apply the rule to all projects within the domain and you check the **Cascade rule to child domain units** option, you thus enable metadata enforcement across child domains, with optional permissions allowing child domains to override the parent domain’s enforced forms. + * Under **Scope** , specify with which data entities you want to associate these forms. You can choose data products and/or data assets. + + * Under **Data asset types** , specify whether the rule applies across all asset types or limit it to selected asset types. + + * Under **Projects** , specify whether the required forms will be associated with data products and/or assets published by all projects or only selected projects in this domain unit. Also, check **Cascade rule to child domain units** if you want child domain units to inherit this requirement.