/AWS1/CL_WAF=>CREATEWEBACLMIGRATIONSTACK()¶
About CreateWebACLMigrationStack¶
Creates an AWS CloudFormation WAFV2 template for the specified web ACL in the specified Amazon S3 bucket. Then, in CloudFormation, you create a stack from the template, to create the web ACL and its resources in AWS WAFV2. Use this to migrate your AWS WAF Classic web ACL to the latest version of AWS WAF.
This is part of a larger migration procedure for web ACLs from AWS WAF Classic to the latest version of AWS WAF. For the full procedure, including caveats and manual steps to complete the migration and switch over to the new web ACL, see Migrating your AWS WAF Classic resources to AWS WAF in the AWS WAF Developer Guide.
Method Signature¶
IMPORTING¶
Required arguments:¶
IV_WEBACLID TYPE /AWS1/WAFRESOURCEID /AWS1/WAFRESOURCEID¶
The UUID of the WAF Classic web ACL that you want to migrate to WAF v2.
IV_S3BUCKETNAME TYPE /AWS1/WAFS3BUCKETNAME /AWS1/WAFS3BUCKETNAME¶
The name of the Amazon S3 bucket to store the CloudFormation template in. The S3 bucket must be configured as follows for the migration:
The bucket name must start with
aws-waf-migration-. For example,aws-waf-migration-my-web-acl.The bucket must be in the Region where you are deploying the template. For example, for a web ACL in us-west-2, you must use an Amazon S3 bucket in us-west-2 and you must deploy the template stack to us-west-2.
The bucket policies must permit the migration process to write data. For listings of the bucket policies, see the Examples section.
IV_IGNOREUNSUPPORTEDTYPE TYPE /AWS1/WAFIGNOREUNSUPPORTEDTYPE /AWS1/WAFIGNOREUNSUPPORTEDTYPE¶
Indicates whether to exclude entities that can't be migrated or to stop the migration. Set this to true to ignore unsupported entities in the web ACL during the migration. Otherwise, if AWS WAF encounters unsupported entities, it stops the process and throws an exception.