Merge pull request #71 from G-Lenz/main

release v2.7.0

Author: tbelmega

CHANGELOG.md

@@ -1,9 +1,21 @@
 # Change Log
  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.7.0] - 2024-07
+### Added
+- Workspace performance metrics
+- DynamoDB tables for workspace data and for individual user sessions
+- Auto-updating container image for most recent patches up to next minor release
+- Private subnets for Fargate container
+- Powertools logging
+- Operational insights CloudWatch dashboard
+- Support for G4DN workspaces
+### Fixed
+- sts token expired after one hour
+
 ## [2.6.6] - 2024-07
 ### Fixed
 - Updated the base python image in the Dockerfile used to mitigate [CVE-2023-50387](https://security-tracker.debian.org/tracker/CVE-2023-50387), [CVE-2023-5678](https://security-tracker.debian.org/tracker/CVE-2023-5678), [CVE-2024-0727](https://security-tracker.debian.org/tracker/CVE-2024-0727), [CVE-2023-6129](https://security-tracker.debian.org/tracker/CVE-2023-6129) and several low severity vulnerabilities
@@ -42,7 +54,7 @@
  ### Fixed
  - Changed the Object Ownership for logging bucket from 'Object writer' to 'Bucket owner enforced' to mitigate the impact caused by new S3 default settings.
  - Updated S3 bucket policy to support access logging.
- 
+
 ## [2.6.1] - 2023-04
  ### Added
  - Added support to block customer misconfiguration for 'Terminate Unused Workspaces' feature. The feature will terminate workspaces only on the last day of the month to avoid accidental termination due to misconfiguration.
@@ -67,36 +79,34 @@
 
  ## [2.4.1] - 2021-10
  - Fixed the bug to get all the workspaces in a directory
- 
+
  ## [2.4] - 2021-09
  ### Fixed
  - Fixed the bug to correctly calculate billable hours if user disconnects workspace within autostop timeout
- 
+
  ### Added
  - Feature to terminate unused workspaces
  - Generate aggregated reports
  - Feature to specify AWS Regions to monitor
  - Support for Gov cloud partition
- 
+
  ## [2.3] - 2021-06
  ### Fixed
  - Fixed the bug to catch InvalidResourceException during the modify_workspace API Call
  - Fixed the bug to catch the Timeout error when sending solution metrics
- 
+
  ### Added
  - Feature to support using existing VPC for ECS task
  - Calculate ADMIN_MAINTENANCE hours and add it to final billable hours
  - Added new columns to the daily report
- - Improved the accuracy to calculate billable hours 
- 
+ - Improved the accuracy to calculate billable hours
+
  ## [2.2.1] - 2020-04-22
  ### Fixed
  - Removed the the api call for describe_workspace_bundles to address the throttling issue
  - Changed the metric to calculate billable hours from "Stopped" to "UserConnected"
- 
+
  ## [2.2.0] - 2019-11-12
  ### Added
 - Made tagging case insensitive
 - Removed duplicate handler in CF
-
-

CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
 ## Code of Conduct
-This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 [email protected] with any additional questions or comments.

CONTRIBUTING.md

@@ -1,17 +1,17 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional 
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
 documentation, we greatly value feedback and contributions from our community.
 
-Please read through this document before submitting any issues or pull requests to ensure we have all the necessary 
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
 information to effectively respond to your bug report or contribution.
 
 
 ## Reporting Bugs/Feature Requests
 
 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/cost-optimizer-for-amazon-workspaces/issues), or [recently closed](https://github.com/aws-solutions/cost-optimizer-for-amazon-workspaces/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/cost-optimizer-for-amazon-workspaces/issues), or [recently closed](https://github.com/aws-solutions/cost-optimizer-for-amazon-workspaces/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
@@ -36,17 +36,17 @@ To send us a pull request, please:
 5. Send us a pull request, answering any default questions in the pull request interface.
 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
-GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and 
+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/cost-optimizer-for-amazon-workspaces/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/cost-optimizer-for-amazon-workspaces/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). 
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 [email protected] with any additional questions or comments.