AWS prescriptive-guidance documentation change
Summary
Removed '(IaC)' acronym from infrastructure-as-code recommendation while maintaining the same security guidance.
Security assessment
Change is purely editorial (acronym removal) without altering security substance. The existing security recommendation for automated controls remains unchanged and isn't enhanced.
Diff
diff --git a/prescriptive-guidance/latest/appstream-well-architected-framework/security.md b/prescriptive-guidance/latest/appstream-well-architected-framework/security.md index 812c9b171..1a8ca750f 100644 --- a//prescriptive-guidance/latest/appstream-well-architected-framework/security.md +++ b//prescriptive-guidance/latest/appstream-well-architected-framework/security.md @@ -157 +157 @@ Use automated, code-defined security controls in version-controlled templates to - * Use infrastructure as code (IaC) by using services such as AWS CloudFormation to implement consistent security configurations across all fleet deployments. For more information, see the AWS blog post [Automatically attach additional security groups to Amazon WorkSpaces Applications and Amazon WorkSpaces](https://aws.amazon.com/blogs/desktop-and-application-streaming/automatically-attach-additional-security-groups-to-amazon-appstream-2-0-and-amazon-workspaces/). + * Use infrastructure as code by using services such as AWS CloudFormation to implement consistent security configurations across all fleet deployments. For more information, see the AWS blog post [Automatically attach additional security groups to Amazon WorkSpaces Applications and Amazon WorkSpaces](https://aws.amazon.com/blogs/desktop-and-application-streaming/automatically-attach-additional-security-groups-to-amazon-appstream-2-0-and-amazon-workspaces/).