Merge pull request #43 from aws-solutions/release/v2.1.0

Upgrade to v2.1.0

Author: tbelmega

.github/ISSUE_TEMPLATE/bug_report.md

@@ -22,7 +22,7 @@ assignees: ""
 
 - [ ] Version: [e.g. v2.0.0]
 
-To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "_(SO0134) - The AWS CloudFormation template for deployment of the Automations for AWS Firewall Manager. Version **v2.0.0**_". You can also find the version from [releases](https://github.com/aws-solutions/aws-firewall-manager-automations-for-aws-organizations/releases)
+To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "_(SO0134) - The AWS CloudFormation template for deployment of the Automations for AWS Firewall Manager. Version **v2.0.0**_". You can also find the version from [releases](https://github.com/aws-solutions/automations-for-aws-firewall-manager/releases)
 
 - [ ] Region: [e.g. us-east-1]
 - [ ] Was the solution modified from the version published on this repository?

.gitignore

@@ -7,6 +7,7 @@
 global-s3-assets
 regional-s3-assets
 open-source
+/deployment/setenv.sh
 
 # Generated ouputs
 dist

CHANGELOG.md

@@ -5,26 +5,62 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.1.0] - 2024-06-17
+
+### Added
+
+- Support for China regions.
+- Support for GovCloud regions.
+- Support for Opt-in regions.
+- Policies will now update automatically when a new version of policy_manifest.json file is uploaded to the solution's `PolicyManifest` S3 bucket.
+- Automations for AWS Shield Advanced subscribers to set up health-based detection and proactive engagement. This includes three new CloudFormation templates: `aws-fms-shield-automations-prereq`, `aws-fms-shield-automations`, and `aws-fms-proactive-event-response`.
+- Option to subscribe to SNS topic for error notifications.
+- Integration with Amazon X-Ray.
+- Lambda layer for utilities shared by solution's lambda functions.
+- Snapshots for CDK stacks in `source/resources/__tests__`.
+- upload-s3-dist.sh script to the `/deployment` directory to upload solution artifacts directly to S3.
+
+### Changed
+
+- Updated default policy_manifest.json to enable AWS Shield Advanced automatic application-layer DDoS protection in "count" mode for Shield Advanced policies deployed by the solution via Firewall Manager. Currently, AWS Shield supports this feature for CloudFront distributions and Application Load Balancers only.
+- General refactor to increase code and unit test clarity.
+- `policyUpdateToken` is no longer stored in DynamoDB, instead it is retrieved using FMS GetPolicy API.
+- Removed anonymized metrics publishing from PreReqManager Lambda function.
+- Removed UUID from the Prerequisite stack.
+- Updated wording from "anonymous" to "anonymized" for metric publishing.
+- Removed `MetricsQueue` resource & `MetricsManager` Lambda function and consolidated metrics publishing to the `utilsLayer`.
+- Enhanced log statements to use Lambda Powertools Logger.
+- Enhanced SSM Parameter retrieval to use Lambda Powertools.
+- Upgraded dependencies with `npm upgrade`.
+
+### Fixed
+
+- Fixed bug in Prerequisite stack which halted AWS Organizations trusted access with CloudFormation StackSets from being activated.
+
 ## [2.0.12] - 2024-09-19
 
 ### Security
-- Upgrade depdendencies to mitigate [CVE-2024-45296](https://nvd.nist.gov/vuln/detail/CVE-2024-45296)
 
+- Upgrade depdendencies to mitigate [CVE-2024-45296](https://nvd.nist.gov/vuln/detail/CVE-2024-45296)
 
 ## [2.0.11] - 2024-08-01
 
 ### Security
+
 - Upgrade `fast-xml-parser` to mitigate [CVE-2024-41818](https://nvd.nist.gov/vuln/detail/CVE-2024-41818)
 
 ### Changed
+
 - Extended PolicyManager's Log Group retention period to ten years.
 
 ## [2.0.10] - 2024-06-19
 
 ### Security
+
 - Upgraded `braces` package to mitigate [CVE-2024-4068](https://avd.aquasec.com/nvd/2024/cve-2024-4068/)
 
 ### Fixed
+
 - Fixed intermittent deployment failure caused by "CopyManifest" custom resource installing latest SDK version.
 
 ## [2.0.9] - 2024-01-07

CONTRIBUTING.md

@@ -11,7 +11,7 @@ information to effectively respond to your bug report or contribution.
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check [existing open](https://github.com/aws-solutions/aws-firewall-manager-automations-for-aws-organizations/issues), or [recently closed](https://github.com/aws-solutions/aws-firewall-manager-automations-for-aws-organizations/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
+When filing an issue, please check [existing open](https://github.com/aws-solutions/automations-for-aws-firewall-manager/issues), or [recently closed](https://github.com/aws-solutions/automations-for-aws-firewall-manager/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
 reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
@@ -41,7 +41,7 @@ GitHub provides additional document on [forking a repository](https://help.githu
 
 
 ## Finding contributions to work on
-Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws-solutions/aws-firewall-manager-automations-for-aws-organizations/labels/help%20wanted) issues is a great place to start.
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws-solutions/automations-for-aws-firewall-manager/labels/help%20wanted) issues is a great place to start.
 
 
 ## Code of Conduct
@@ -56,6 +56,6 @@ If you discover a potential security issue in this project we ask that you notif
 
 ## Licensing
 
-See the [LICENSE](https://github.com/aws-solutions/aws-firewall-manager-automations-for-aws-organizations/blob/main/LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+See the [LICENSE](https://github.com/aws-solutions/automations-for-aws-firewall-manager/blob/main/LICENSE.txt) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
 
-We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
+We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.