AWS waf documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in migration procedure description
Security assessment
This is a terminology standardization change. The migration process documentation remains functionally identical with no security implications.
Diff
diff --git a/waf/latest/developerguide/waf-migrating-procedure.md b/waf/latest/developerguide/waf-migrating-procedure.md index d921fcbd0..435462cbc 100644 --- a//waf/latest/developerguide/waf-migrating-procedure.md +++ b//waf/latest/developerguide/waf-migrating-procedure.md @@ -19 +19 @@ The following lists the high-level steps for migrating a protection pack (web AC - 1. The automated migration reads everything related to your existing protection pack (web ACL), without modifying or deleting anything in AWS WAF Classic. It creates a representation of the web ACL and its related resources, compatible with AWS WAF. It generates an AWS CloudFormation template for the new protection pack (web ACL) and stores it in an Amazon S3 bucket. + 1. The automated migration reads everything related to your existing protection pack (web ACL), without modifying or deleting anything in AWS WAF Classic. It creates a representation of the web ACL and its related resources, compatible with AWS WAF. It generates an CloudFormation template for the new protection pack (web ACL) and stores it in an Amazon S3 bucket. @@ -21 +21 @@ The following lists the high-level steps for migrating a protection pack (web AC - 2. You deploy the template into AWS CloudFormation, in order to recreate the protection pack (web ACL) and related resources in AWS WAF. + 2. You deploy the template into CloudFormation, in order to recreate the protection pack (web ACL) and related resources in AWS WAF.