AWS lookout-for-equipment documentation change
Summary
Replaced 'AWS services' with 'Amazon Web Services services' in data protection guidance
Security assessment
Change is purely terminological (branding consistency). The existing security recommendation about credential handling remains unchanged.
Diff
diff --git a/lookout-for-equipment/latest/ug/data-protection.md b/lookout-for-equipment/latest/ug/data-protection.md index 0ad4240e8..3509132ac 100644 --- a//lookout-for-equipment/latest/ug/data-protection.md +++ b//lookout-for-equipment/latest/ug/data-protection.md @@ -26 +26 @@ For data protection purposes, we recommend that you protect AWS account credenti -We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a `Name` field. This includes when you work with Amazon Lookout for Equipment or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into Amazon Lookout for Equipment or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don't include credentials information in the URL to validate your request to that server. +We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a `Name` field. This includes when you work with Amazon Lookout for Equipment or other Amazon Web Services services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into Amazon Lookout for Equipment or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don't include credentials information in the URL to validate your request to that server.