Merge pull request #206 from sanjay-reddy-kandi/main

release/v6.3.0

CHANGELOG.md

@@ -5,64 +5,99 @@ 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).
 
+## [6.3.0] - 2024-11-22
+
+### Added
+
+- Simulation capability for quota utilization events to test notification workflows
+- Configurable monitoring for SageMaker and Connect services
+- Optional Spoke notification stack for localized alerts
+- Support for AWS GCR Regions
+- Link to quota limit increase request in email/Slack notifications
+- Custom quota threshold value input option
+
+### Changed
+
+- In ORG/HYBRID mode, Resetting SSM parameters to NOP now triggers:
+  - Deletion of stack instances
+  - Clearing of event bus permissions
+- In HYBRID mode, deployment now proceeds with valid entries from either the OU ID list or the Account ID list, rather than requiring both to be valid
+- Made SNS notifications human readable
+
+### Fixed
+
+- GitHub Issues [#155](https://github.com/aws-solutions/quota-monitor-for-aws/issues/155), [#157](https://github.com/aws-solutions/quota-monitor-for-aws/issues/157), [#177](https://github.com/aws-solutions/quota-monitor-for-aws/issues/177), [#187](https://github.com/aws-solutions/quota-monitor-for-aws/issues/187), and [#202](https://github.com/aws-solutions/quota-monitor-for-aws/issues/202)
+
 ## [6.2.11] - 2024-10-10
 
 ### Changed
+
 - Add batching to getQuotasWithUtilizationMetrics function
 - Refactor _putMonitoredQuotas function to use batch writes
 - Changed the memory allocation for the QMListManager Lambda function to 256 MB
 - Added better error handling for CloudWatch ValidationErrors, with attempt to identify problematic quotas
 
 ### Fixed
+
 - GitHub Issues [#200](https://github.com/aws-solutions/quota-monitor-for-aws/issues/200) and [#201](https://github.com/aws-solutions/quota-monitor-for-aws/issues/201)
 
 ## [6.2.10] - 2024-09-18
 
 ### Fixed
+
 - Update path-to-regexp to address [CVE-2024-45296](https://nvd.nist.gov/vuln/detail/CVE-2024-45296)
 - Update micromatch to address [CVE-2024-4067](https://nvd.nist.gov/vuln/detail/CVE-2024-4067)
 
 ## [6.2.9] - 2024-07-31
 
 ### Fixed
+
 - Update fast-xml-parser to address [CVE-2024-41818](https://nvd.nist.gov/vuln/detail/CVE-2024-41818)
 
 ## [6.2.8] - 2024-06-26
 
 ### Fixed
+
 - Update dependency to address [CVE-2024-4068](https://avd.aquasec.com/nvd/cve-2024-4068)
 
 ## [6.2.7] - 2024-06-10
 
 ### Fixed
+
 - Added batching to get getMetricData calls to avoid limits
 - Added quotaCode to metric Ids to avoid duplicate Ids.
 
 ## [6.2.6] - 2024-03-18
 
 ### Changed
+
 - First of month schedule for quotaListManager Lambda function changed to every 30 days
 - Add rate limiting delay between listServiceQuota API calls
 - Add page size to Service Quotas API calls
 
 ### Fixed
+
 - GitHub Issue [#183](https://github.com/aws-solutions/quota-monitor-for-aws/issues/183), PR [#147](https://github.com/aws-solutions/quota-monitor-for-aws/pull/47) - fix expiration of DynamoDB records
 
 ## [6.2.5] - 2024-01-08
 
 ### Changed
+
 - Made reporting of OK Messages optional
 - Added percentage marker on Service Quota notifications
 
 ### Fixed
+
 - Added manual resource cleanup after sqs message consumption
 
 ## [6.2.4] - 2023-11-09
 
 ### Changed
+
 - Scoped permissions down for Stackset operations
 
 ### Fixed
+
 - [Error](https://github.com/aws-solutions/quota-monitor-for-aws/issues/172) in saving notifications to summary table
 
 ## [6.2.3] - 2023-10-24
@@ -74,31 +109,38 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [6.2.2] - 2023-08-16
 
 ### Added
+
 - Service Quotas spoke template parameters exposed in the hub template too
 
 ### Changed
+
 - Lambda run times upgraded to Node.js18
 - Dependency updates
 
-
 ## [6.2.1] - 2023-06-28
+
 ### Changed
+
 - Dependency updates addressing [CVE-2023-26920](https://cwe.mitre.org/data/definitions/1321.html)
 
 ## [6.2.0] - 2023-06-01
 
 ### Added
+
 - Support for monitoring resources with Service Catalog AppRegistry
 
 ### Changed
+
 - Customer Managed Keys for the resources in hub stacks
 
 ### Fixed
+
 - Bugs resulting in dynamoDb tables not being populated
 
 ## [6.1.0] - 2023-04-05
 
 ### Added
+
 - Support for monitoring all usage reporting quotas from all services supported by Service Quotas
 - Ability to mute selected notifications
 - Support for GovCloud regions
@@ -107,6 +149,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Allow customization to Stack Set deployments configuration
 
 ### Changed
+
 - Use AWS Managed keys for the resources in the templates to help reduce the cost of deployment.
 
 ## [6.0.0] - 2022-10-14

CONTRIBUTING.md

@@ -10,7 +10,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/quota-monitor-for-aws/issues), or [recently closed](https://github.com/aws-solutions/quota-monitor-for-aws/issues?q=is%3Aissue+is%3Aclosed), issues to make sure somebody else hasn't already
+When filing an issue, please check [existing open](https://github.com/aws-solutions/quota-monitor-for-aws/issues), or [recently closed](https://github.com/aws-solutions/quota-monitor-for-aws/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
@@ -38,6 +38,10 @@ To send us a pull request, please:
 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
+## 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/quota-monitor-for-aws/labels/help%20wanted) issues is a great place to start.
+
 ## Code of Conduct
 
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
@@ -52,4 +56,4 @@ If you discover a potential security issue in this project we ask that you notif
 
 See the [LICENSE](https://github.com/aws-solutions/quota-monitor-for-aws/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.