[AWS Solution Retirement Notice] Research Service Workbench on AWS will be retired on 2024-11-30.
The AWS Solutions team would like to inform you that the functionality provided by Research Service Workbench on AWS has been superseded with functionality in Research and Engineering Studio.
Research and Engineering Studio (RES) is an AWS supported, open source product that enables IT administrators to provide a web portal for scientists and engineers to run technical computing workloads on AWS. RES provides a single pane of glass for users to launch secure virtual desktops to conduct scientific research, product design, engineering simulations, or data analysis workloads. RES offers similar functionality to manage data access for researchers by projects and Virtual desktops to access the data. RES offers additional new capabilities such as file systems and integration with High Performance computing services. More information is available via Research and Engineering Studio documentation here.
On 2024-11-30, AWS support for Research Service Workbench on AWS will end, and the GitHub repository will be archived. You will no longer be able to deploy Research Service Workbench on AWS via Cloudformation template within the AWS Console after this date.
Existing deployments will continue to run. If you have deployed Research Service Workbench on AWS via cloning GitHub open source code, you may continue to use the solution. If underlying service APIs change after solution support ends, deployments may error or may not be possible to stop / start.
Research Service Workbench on AWS is a backend API designed to empower AWS partners to more easily build self-service portals for research institutions, allowing their researchers to create and manage secure research computing environments. RSW builds on AWS services including Amazon S3, Service Catalog, and AWS Systems Manager to deliver comprehensive, cutting-edge capabilities in less time while meeting the high bar for security and governance demanded by regulators and funding agencies.
Using a custom built portal provided by a partner, built on Research Service Workbench, research IT departments can more easily work with partners to deliver a self-service portal with a comprehensive catalog of tools tailored to the needs of the researchers they support. Using a portal built using RSW, researchers can create, access, and retire environments without needing to be experts on cloud infrastructure or security. They can work individually or collaborate with others on the same data, with RSW securely orchestrating the connection of research environments to Amazon S3. Furthermore, environments are deployed in specific AWS accounts and Amazon Virtual Private Clouds (VPCs), allowing connectivity to resources on and off campus. Institutions are fully in control of their data, data flows, and AWS footprint. They can scale investments in IT and security across multiple research programs, reducing duplicate effort and freeing up resources to focus on science.
To learn more about FWoA and how to deploy, refer to the Research Service Workbench Implementation Guide.
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 information to effectively respond to your bug report or contribution.
In order to start developement please refer to Development Instructions
| Folder | Package | README |
|---|---|---|
| solutions/swb-app | [@aws/swb-app] | README |
| solutions/swb-reference | [@aws/swb-reference] | README |
| workbench-core/accounts | [@aws/workbench-core-accounts] | README |
| workbench-core/audit | [@aws/workbench-core-audit] | README |
| workbench-core/authentication | [@aws/workbench-core-authentication] | README |
| workbench-core/authorization | [@aws/workbench-core-authorization] | README |
| workbench-core/base | [@aws/workbench-core-base] | README |
| workbench-core/datasets | [@aws/workbench-core-datasets] | README |
| workbench-core/environments | [@aws/workbench-core-environments] | README |
| workbench-core/infrastructure | [@aws/workbench-core-infrastructure] | README |
| workbench-core/logging | [@aws/workbench-core-logging] | README |
| workbench-core/user-management | [@aws/workbench-core-user-management] | README |
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' issues is a great place to start.
This project has adopted the Amazon Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our vulnerability reporting page. Please do not create a public github issue.
See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.
This solution collects anonymous operational metrics to help AWS improve the quality of features of the solution. For more information, including how to disable this capability, please see the Implementation Guide.