Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update aws-firewall-factory 4.1.0 #178

Merged
merged 1 commit into from
Sep 19, 2023
Merged

Update aws-firewall-factory 4.1.0 #178

merged 1 commit into from
Sep 19, 2023

Conversation

goyertp
Copy link
Contributor

@goyertp goyertp commented Sep 19, 2023

Change Log

Released

4.1.0

Added

  • This update presents a new feature that centralizes the management of RegexPatternSet. With this improvement, manual updates of regexpatternset across multiple AWS accounts are no longer necessary. Users can now define the feature in code and replicate it for use by WAF rules wherever applicable.
  • Additionally, cdk destroy has been included in the taskfile.
  • Furthermore, we have modified several enums to enhance their ease of with previous versions: use while maintaining downward compatibility, such as
    • WebAclScope
    • AwsManagedRules
    • ManagedRuleGroupVendor
    • CustomResponseBodiesContentType
    • WebAclTypeEnum
  • uuidFirewallFactoryResourceIdentitfier: Introducing a firewall identifier UUID that will be utilized for resource names in AWS.

Fixed

  • Capacity and version information for Managed Rule Groups are now optional. We calculate the capacity on the fly, so specifying capacity is unnecessary. If no version is provided, we will retrieve the latest version for the Managed Rule Group using the API.
  • DeliveryStreamName not checked - Erroneous if exceeding 64 character limit source.
  • Fixed nonfunctional documentation links.

Removed

  • Export names from CloudFormation stack outputs, as we rely on the stack name and output names from the particular CloudFormation stack to obtain the necessary information. ## 4.0.0

Added

  • A custom resource to retrieve the latest version of the ManagedRuleGroup and check if the specified version is valid.

# Change Log

## Released
## 4.0.1

### Added
- This update presents a new feature that centralizes the management of RegexPatternSet. With this improvement, manual updates of regexpatternset across multiple AWS accounts are no longer necessary.
  Users can now define the feature in code and replicate it for use by WAF rules wherever applicable.
- Additionally, cdk destroy has been included in the taskfile.
- Furthermore, we have modified several enums to enhance their ease of with previous versions: use while maintaining downward compatibility, such as
  - WebAclScope
  - AwsManagedRules
  - ManagedRuleGroupVendor
  - CustomResponseBodiesContentType
  - WebAclTypeEnum
- uuidFirewallFactoryResourceIdentitfier: Introducing a firewall identifier UUID that will be utilized for resource names in AWS.

### Fixed
- Capacity and version information for Managed Rule Groups are now optional. We calculate the capacity on the fly, so specifying capacity is unnecessary. If no version is provided, we will retrieve the latest version for the Managed Rule Group using the API.
- DeliveryStreamName not checked - Erroneous if exceeding 64 character limit [source](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kinesisfirehose-deliverystream.html#cfn-kinesisfirehose-deliverystream-deliverystreamname).
- Fixed nonfunctional documentation links.

### Removed
- Export names from CloudFormation stack outputs, as we rely on the stack name and output names from the particular CloudFormation stack to obtain the necessary information.
## 4.0.0
### Added
- A custom resource to retrieve the latest version of the ManagedRuleGroup and check if the specified version is valid.
@daknhh daknhh merged commit d5404d0 into globaldatanet:master Sep 19, 2023
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants