Target multiple resources type with wildcard configuration for AWS CloudFormation Hooks
Today, AWS CloudFormation Hooks launches wildcard resource type for Hook configurations enabling customers to match multiple resources types. Customers can use wildcards to define resources targets for building flexible Hooks. Such Hooks can activate for resource types which are not explicitly known when the Hook was created. For example, customers can use AWS::ECR::* wildcard to define a Hook that triggers for all resource types under Amazon ECR.
Today, AWS CloudFormation Hooks launches wildcard resource type for Hook configurations enabling customers to match multiple resources types. Customers can use wildcards to define resources targets for building flexible Hooks. Such Hooks can activate for resource types which are not explicitly known when the Hook was created. For example, customers can use AWS::ECR::* wildcard to define a Hook that triggers for all resource types under Amazon ECR.
With this launch, customers can select a list of resource targets using “*” wildcard character, and match for prefix, infix, and suffix. For example, customers can select all resource types starting with AWS::S3 such as AWS::S3::AccessPoint, AWS::S3Outposts::Bucket, etc. with wildcard AWS::S3*. This allows customer to automate resource validation to alert and/or prevent the provisioning operation of non-compliant resources.
The feature is generally available in the following AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Africa (Cape Town), Asia Pacific (Hong Kong, Mumbai, Osaka, Seoul, Singapore, Sydney, Tokyo), Canada (Central), Europe (Frankfurt, Ireland, London, Milan, Paris, Stockholm), Middle East (Bahrain), and South America (São Paulo).
To learn more, refer to the User Guide and API reference.