AWS entityresolution documentation change
Summary
Restructured documentation for processing cadence options and clarified 'Index only for ID mapping' functionality. Updated comparison type explanations and output field management instructions.
Security assessment
Changes focus on workflow configuration clarity rather than security controls. The 'Index only for ID mapping' clarification improves operational understanding but doesn't address vulnerabilities or introduce security features.
Diff
diff --git a/entityresolution/latest/userguide/creating-matching-workflow-rule-based.md b/entityresolution/latest/userguide/creating-matching-workflow-rule-based.md index eef00c464..0bd9009fb 100644 --- a//entityresolution/latest/userguide/creating-matching-workflow-rule-based.md +++ b//entityresolution/latest/userguide/creating-matching-workflow-rule-based.md @@ -69 +69 @@ Option | Recommended action - 2. For **Processing cadence** , choose one of the following options based on your goal. + 2. For **Processing cadence** , select one of the following options: @@ -71,4 +71,3 @@ Option | Recommended action -Your goal | Recommended option ----|--- -Run a workflow on demand for a bulk update | **Manual** -Run a workflow as soon as new data is in your S3 bucket | **Automatic** + * Choose **Manual** to run a workflow on demand for a bulk update + + * Choose **Automatic** to run a workflow as soon as new data is in your S3 bucket @@ -80 +79 @@ If you choose **Automatic** , ensure that you have Amazon EventBridge notificati - 3. (Optional) For **Index only for ID mapping** , You can choose to **Turn on** the ability to only index the data and not generate IDs. + 3. (Optional) Select **Turn on** for **Index only for ID mapping** , if you want to use the matching workflow as a source or target in an ID mapping workflow. AWS Entity Resolution will only index the data and not generate IDs. @@ -90 +89 @@ You can create up to 15 rules and you can apply up to 15 different match keys ac - 5. For **Comparison type** , choose one of the following options based on your goal. + 5. Choose **Add another rule** to create additional rules as needed. @@ -92,4 +91,5 @@ You can create up to 15 rules and you can apply up to 15 different match keys ac -Your goal | Recommended option ----|--- -Find any combination of matches across data stored in multiple input fields | **Multiple input fields** -Limit comparison to a single input field | **Single input field** + 6. For **Comparison type** , select one of the following options: + + * Choose **Multiple input fields** to find any combination of matches across data stored in multiple input fields. + + * Choose **Single input field** to limit comparison to a single input field. @@ -99 +99 @@ Limit comparison to a single input field | **Single input field** - 6. Choose **Next**. + 7. Choose **Next**. @@ -109 +109 @@ Limit comparison to a single input field | **Single input field** - 4. For **Data output** , decide which fields you want to include, hide, or mask, and then take the recommended actions based on your goals. + 4. For **Data output** , decide which fields you want to include, hide, or mask, and then select one of the following options: @@ -111,6 +111,7 @@ Limit comparison to a single input field | **Single input field** -Your goal | Recommended option ----|--- -Include fields | Keep the output state as **Included**. -Hide fields (exclude from output) | Choose the **Output field** , and then choose **Hide**. -Mask fields | Choose the **Output field** , and then choose **Hash output**. -Reset the previous settings | Choose **Reset**. + * Keep the output state as **Included** to include fields. + + * Choose the **Output field** , and then choose **Hide** to hide fields (exclude from output) + + * Choose the **Output field** , and then choose **Hash output** to mask fields. + + * Choose **Reset** to reset the previous settings.