Releases: aws-solutions/instance-scheduler-on-aws
Releases · aws-solutions/instance-scheduler-on-aws
v1.5.5
[1.5.5] -- 2024-04-12
Security
- Upgrade Black to mitigate CVE-2024-21503
- Upgrade idna to mitigate CVE-2024-3651
v1.5.4
[1.5.4] -- 2024-02-29
Security
- Upgrade cryptography to mitigate CVE-2024-26130, CVE-2023-50782, CVE-2024-0727, CVE-2023-49083
- Upgrade Jinja to mitigate CVE-2024-22195
- Upgrade Werkzeug to mitigate CVE-2023-46136
- Upgrade IP to mitigate CVE-2023-42282
- Remove ecdsa to mitigate CVE-2024-23342
v1.5.3
[1.5.3] - 2023-10-22
Security
- Upgrade @babel/traverse to mitigate CVE-2023-45133
- Upgrade urllib3 to mitigate CVE-2023-45803
v1.5.2
[1.5.2] - 2023-10-9
Security
- Upgrade cryptography to mitigate GHSA-v8gr-m533-ghj9 and GHSA-jm77-qphf-c4w8
- Upgrade urllib3 to mitigate CVE-2023-43804
- Upgrade certifi to mitigate CVE-2023-37920
v1.5.1
[1.5.1] - 2023-07-24
Changed
- Add a default start and stop tag
- Use EC2 API more efficiently when filtering EC2 instances for scheduling
- Use system tzdata instead of pytz
- Upgrade Python runtime to 3.10
- Package CLI as sdist and wheel
- Refactoring, type hinting, and improved testing
- Add projen for managing project configuration
Fixed
- Restore Python 3.8 support to CLI
- Fix bug starting EC2 instances at least 10 minutes before maintenance windows
- Fix bug targeting RDS instances that are part of an Aurora cluster for scheduling
- Fix bug where EC2 instances failing to start or stop cause an entire batch to fail to start or stop
- Fix bug where the instance type field on a period in a CloudFormation schedule has no effect
- Fix bug creating CloudWatch log streams when hub scheduling is disabled
Security
- Upgrade cryptography to mitigate CVE-2023-38325 and CVE-2023-2650
- Upgrade aws-cdk-lib to mitigate CVE-2023-35165
- Upgrade fast-xml-parser to mitigate CVE-2023-34104
- Upgrade requests to mitigate CVE-2023-32681
- Upgrade word-wrap to mitigate CVE-2023-26115
- Upgrade semver to mitigate CVE-2022-25883
v1.5.0
Added
- Enable solution to support deployment using organization id.
- Solution now deployable with CDK deploy
- Development/e2e testing pipeline included under source/infrastructure/pipeline capable of automatically deploying and testing solution.
- App Registry integration
Updated
- Boto Retry module could cause unintended high lambda utilization in case of API failures.
- Cross account scheduling no longer requires IAM role name but only account id.
Removed
- override_status flag on schedules has been deprecated
v1.4.2
[1.4.2] - 2023-01-11
Fixed
- Upgrade certifi to mitigate CVE-2022-23491.
- Updated issues in bandit scan.
- Updated the CDK version 2.x
v1.4.1
v1.4.0
Added
- Enable solution to be deployed as mutliple stacks in the same account/region
Fixed
- Fix the SSM Maintenance window issue where solution was not fetching SSM Maintenance windows from other account/regions
- Updated logging utility to remove incorrect timestamp
- Fixed issue with scheduler stopping instances at UTC time even when configured with other timezones and Period having weekday configured as Wed#4. Github Issue
- Modified Anonymous Data reporting refer implementation guide for details.
- Removed redundant logging of UTC timestamp along with the Account/Region default stamp in logs in AWS CloudWatch.
- Fixed Github Issue for scheduler-cli.
v1.3.3 - CDK Build
v1.3.3-Patch Patching bin folders