Skip to content

Commit f0b61d2

Browse files
authored
Merge pull request #206 from sanjay-reddy-kandi/main
release/v6.3.0
2 parents 7727b5f + a044754 commit f0b61d2

File tree

136 files changed

+15044
-3608
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

136 files changed

+15044
-3608
lines changed

CHANGELOG.md

Lines changed: 44 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,64 +5,99 @@ All notable changes to this project will be documented in this file.
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

8+
## [6.3.0] - 2024-11-22
9+
10+
### Added
11+
12+
- Simulation capability for quota utilization events to test notification workflows
13+
- Configurable monitoring for SageMaker and Connect services
14+
- Optional Spoke notification stack for localized alerts
15+
- Support for AWS GCR Regions
16+
- Link to quota limit increase request in email/Slack notifications
17+
- Custom quota threshold value input option
18+
19+
### Changed
20+
21+
- In ORG/HYBRID mode, Resetting SSM parameters to NOP now triggers:
22+
- Deletion of stack instances
23+
- Clearing of event bus permissions
24+
- 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
25+
- Made SNS notifications human readable
26+
27+
### Fixed
28+
29+
- 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)
30+
831
## [6.2.11] - 2024-10-10
932

1033
### Changed
34+
1135
- Add batching to getQuotasWithUtilizationMetrics function
1236
- Refactor _putMonitoredQuotas function to use batch writes
1337
- Changed the memory allocation for the QMListManager Lambda function to 256 MB
1438
- Added better error handling for CloudWatch ValidationErrors, with attempt to identify problematic quotas
1539

1640
### Fixed
41+
1742
- 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)
1843

1944
## [6.2.10] - 2024-09-18
2045

2146
### Fixed
47+
2248
- Update path-to-regexp to address [CVE-2024-45296](https://nvd.nist.gov/vuln/detail/CVE-2024-45296)
2349
- Update micromatch to address [CVE-2024-4067](https://nvd.nist.gov/vuln/detail/CVE-2024-4067)
2450

2551
## [6.2.9] - 2024-07-31
2652

2753
### Fixed
54+
2855
- Update fast-xml-parser to address [CVE-2024-41818](https://nvd.nist.gov/vuln/detail/CVE-2024-41818)
2956

3057
## [6.2.8] - 2024-06-26
3158

3259
### Fixed
60+
3361
- Update dependency to address [CVE-2024-4068](https://avd.aquasec.com/nvd/cve-2024-4068)
3462

3563
## [6.2.7] - 2024-06-10
3664

3765
### Fixed
66+
3867
- Added batching to get getMetricData calls to avoid limits
3968
- Added quotaCode to metric Ids to avoid duplicate Ids.
4069

4170
## [6.2.6] - 2024-03-18
4271

4372
### Changed
73+
4474
- First of month schedule for quotaListManager Lambda function changed to every 30 days
4575
- Add rate limiting delay between listServiceQuota API calls
4676
- Add page size to Service Quotas API calls
4777

4878
### Fixed
79+
4980
- 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
5081

5182
## [6.2.5] - 2024-01-08
5283

5384
### Changed
85+
5486
- Made reporting of OK Messages optional
5587
- Added percentage marker on Service Quota notifications
5688

5789
### Fixed
90+
5891
- Added manual resource cleanup after sqs message consumption
5992

6093
## [6.2.4] - 2023-11-09
6194

6295
### Changed
96+
6397
- Scoped permissions down for Stackset operations
6498

6599
### Fixed
100+
66101
- [Error](https://github.com/aws-solutions/quota-monitor-for-aws/issues/172) in saving notifications to summary table
67102

68103
## [6.2.3] - 2023-10-24
@@ -74,31 +109,38 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
74109
## [6.2.2] - 2023-08-16
75110

76111
### Added
112+
77113
- Service Quotas spoke template parameters exposed in the hub template too
78114

79115
### Changed
116+
80117
- Lambda run times upgraded to Node.js18
81118
- Dependency updates
82119

83-
84120
## [6.2.1] - 2023-06-28
121+
85122
### Changed
123+
86124
- Dependency updates addressing [CVE-2023-26920](https://cwe.mitre.org/data/definitions/1321.html)
87125

88126
## [6.2.0] - 2023-06-01
89127

90128
### Added
129+
91130
- Support for monitoring resources with Service Catalog AppRegistry
92131

93132
### Changed
133+
94134
- Customer Managed Keys for the resources in hub stacks
95135

96136
### Fixed
137+
97138
- Bugs resulting in dynamoDb tables not being populated
98139

99140
## [6.1.0] - 2023-04-05
100141

101142
### Added
143+
102144
- Support for monitoring all usage reporting quotas from all services supported by Service Quotas
103145
- Ability to mute selected notifications
104146
- Support for GovCloud regions
@@ -107,6 +149,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
107149
- Allow customization to Stack Set deployments configuration
108150

109151
### Changed
152+
110153
- Use AWS Managed keys for the resources in the templates to help reduce the cost of deployment.
111154

112155
## [6.0.0] - 2022-10-14

CONTRIBUTING.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ information to effectively respond to your bug report or contribution.
1010

1111
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
1212

13-
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
13+
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
1414
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
1515

1616
- A reproducible test case or series of steps
@@ -38,6 +38,10 @@ To send us a pull request, please:
3838
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
3939
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
4040

41+
## Finding contributions to work on
42+
43+
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.
44+
4145
## Code of Conduct
4246

4347
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
5256

5357
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.
5458

55-
We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.
59+
We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.

0 commit comments

Comments
 (0)