Revisions
Date | Change |
---|---|
May 2020 | Initial release |
June 2020 | Release v1.1.0: Added support for AWS Elemental Link. |
December 2020 |
Release v1.2.0: Updated the AWS CloudFormation template; for
more information, refer to
the CHANGELOG.md |
July 2021 |
Release v1.2.1: Bug fixes. For more information, refer to
the
CHANGELOG.md Documentation updates: Expanded the cost estimates to provide more granular information, clarified the collection of operational metrics information, and updated guide organization to improve readability. |
September 2021 |
Release v2.0.0: Bug fixes. For more information, refer to
the CHANGELOG.md |
November 2021 |
Release v2.1.0: Bug fixes. For more information, refer to
the CHANGELOG.md |
January 2022 |
Release v2.1.1: Bug fixes. For more information, refer to
the CHANGELOG.md |
March 2022 |
Release v3.0.0: Updated to use Amazon S3 rather than AWS
MediaStore as live streaming origin. For more information,
refer to the
CHANGELOG.md |
August 2022 |
Release v3.1.0: Bug fixes. For more information, refer to
the
CHANGELOG.md |
November 2022 |
Release v3.1.1: AppRegistry: AppRegistry Application Stack
Association and Application Insights. For more information,
refer to the
CHANGELOG.md |
April 2023 |
Release v3.1.2: Mitigated impact caused by new default
settings for S3 Object Ownership (ACLs disabled) for all new
S3 buckets. For more information, refer to
the CHANGELOG.md |
May 2023 |
Release v3.2.0: Updated Lambda nodes to support Node.js 16.
Added AppRegistry updates to include logical ID. Added
package_lock.json files to packages. Improved security
patching to remediate vulnerable dependencies. Updated
parameter names for consistency. For more information, refer
to
the CHANGELOG.md |
August 2023 |
Release v3.2.1: Updated npm package dependencies in
/source/constructs |
October 2023 |
Release v3.2.2: Updated package versions to resolve security
vulnerabilities. For more information, refer to
the CHANGELOG.md |
November 2023 | Documentation update: Added Confirm cost tags associated with the solution to the Monitoring the solution with AWS Service Catalog AppRegistry section. |