Releases: awslabs/service-workbench-on-aws
v.6.2.3
v6.2.2
v6.2.1
Maintenance Notice
Service Workbench on AWS has been moved to maintenance mode. While in maintenance, we will not add new features to this solution guidance. Security engagement should be directed to AWS Security at [email protected]. If you are new to Service Workbench on AWS, we recommend that you explore using Research and Engineering Studio on AWS (https://aws.amazon.com/hpc/res/). You can get started by following instructions in the Research and Engineering Studio User Guide (https://docs.aws.amazon.com/res/latest/ug/overview.html). If you are an existing customer of Service Workbench on AWS and have additional questions or need immediate help, please contact your AWS Account team.
v6.2.0
In this release, we have addressed GitHub dependabot alerts, upgraded NodeJS to v18, and added IMDSv2 support on AMI creation
Bug Fixes
- add missing dependency (ffb437a)
- backend lambda sdk package (e08dab3)
- minimum patched version of go (36e7714)
- upgrade to node18 (fb39c08)
- remove nodeExternals webpack (c31d7a9)
- semver package version (d51d2bc)
- unit tests for nodeJS16 onwards (c8b3709)
- update node max space (8839635)
- upgrades + modifications for pnpm upgrade (bbc8933)
- use principal.username (e21163f)
- use system context (bee9675)
v6.1.1
v6.1.0
Version 6.1.0 of Service Workbench on AWS brings a security enhancement to improve SWB management of the VPC endpoint policy. The enhancement only applies to customers who enabled AppStream within their environments.
Backwards compatibility:
As part of this release, a new script is included to ensure the new policies are applied to existing accounts and their respective environments. The script can be found in the GitHub Repo and should get executed as follows once all hosting accounts are updated to the latest release:
npm install
npm run update-vpce-with-existing-byob -- <stage-regionAbbreviation-solutionName> <region>
# Example: npm run update-vpce-with-existing-byob -- dev-va-sw us-east-1
Features
v6.0.0
Changes to BYOB studies
Going forward, a BYOB study will always have to be assigned to a SWB project ID. This is to enforce access to the BYOB study's S3 prefix only from its project's linked VPC endpoint.
For upgrade installations
To enforce access to your existing BYOB study from its respective project's VPC endpoint, please perform the following steps:
Before upgrade:
- Terminate all environments that are accessing BYOB studies. This is optional but recommended by the service team.
- Make sure your hosting accounts are in the
Up-to-Datestatus. You can check by visiting theAccountstab on SWB UI and clicking on theAWS Accountstab. If they’re not, please re-onboard the accounts that need updating.
After upgrade:
- Once the new version of SWB has been installed, navigate to the
Data Sourcestab in SWB UI. - On each of the Data Source bucket that has been registered, click on the “CloudFormation” tab, click the
Update Stackbutton, while being logged into the Data Source account console. This will navigate you to the CloudFormation stack for that bucket. Continue with the stack update.
Note:
To continue using existing BYOB studies that were not assigned to a SWB project ID please add a key projectId to that study’s entry in the <stage>-<regionShortName>-<solutionName>-Studies DynamoDB table in the SWB main account with its value equal to the SWB project ID you would like to associate it with. Please work with your AWS partner if you need help.
