AWS datazone documentation change
Summary
Removed 'AWS' prefix from 'AWS CloudFormation templates' to standardize terminology
Security assessment
Change is purely terminological (removing redundant 'AWS' prefix from CloudFormation references). No security implications or modifications to security guidance.
Diff
diff --git a/datazone/latest/userguide/working-with-domain-units.md b/datazone/latest/userguide/working-with-domain-units.md index 184d5ce1b..152d8b5e3 100644 --- a//datazone/latest/userguide/working-with-domain-units.md +++ b//datazone/latest/userguide/working-with-domain-units.md @@ -43 +43 @@ Another way to use the authorization mechanism in Amazon DataZone is to apply au -An Amazon DataZone blueprint configuration is an entity that encapsulates information needed to create and configure resources used in publishing and subscribing user workflows. This information includes AWS account number and region, AWS CloudFormation templates, account level parameters such as VPCs and subnets, and can also contain database connection information and credentials. To control costs and improve security, data platform users require the ability to control who can use these blueprints and create environments. +An Amazon DataZone blueprint configuration is an entity that encapsulates information needed to create and configure resources used in publishing and subscribing user workflows. This information includes AWS account number and region, CloudFormation templates, account level parameters such as VPCs and subnets, and can also contain database connection information and credentials. To control costs and improve security, data platform users require the ability to control who can use these blueprints and create environments.