v1.21.0

Enhancements:

A.External Study:

   1. Users can create both a project account and a study account within the same AWS account.

    2.Users from different organizations can register the same AWS account, designating it solely as a study account.

    3.Users can create a shared study account, and individuals from the same organization should be able to utilize that shared study account.

    4.If a user has data admin privileges, they can create an external study with a project to which they do not have access.

    5.Enable the repair option for a study account when the account status is in error.

    6.When a user onboard an external study or deletes an external study, validate that the study account stack, role, and policy are available in the study account database entry. If available, check if they exist in the corresponding AWS account. If they are not present, throw an error message and update the study account status to error.

    7.Users are not allowed to create an external study with the same bucket name and prefix within the same organization.

    8.When a user clicks on the ‘Register Study’ button, it is essential to validate the chosen bucket region.

    9.Edit external study. This allows users to reuse the studies they create by assigning new projects to the same study. A classic use-case is when a professor wants to use a dataset for a semester project by his students. Each semester the project and students would change but the dataset created as a study would remain the same.

   10. Users should be able to create an external study without choosing any project.

B. The Windows Desktop for Secure Research product allows you to connect via your browser to an EC2 Windows-based desktop machine in the cloud with a modern GUI interface. Data cannot be copied out of the system via clipboard or file-download. All data is encrypted in transit and at rest. A secure research windows based environment intended to allow researchers to access sensitive data under a higher level of control and data protection.

C. Secure Research: Users will be able to update Network details and Egress store details from the 3 dot contextual menu available in project accounts screen for the particular secure account, provided they meet the preset requirements in their Organizational Unit (OU) and upon login.

D. Project Landing page: list the projects of the logged in PI user at first.

Bug-fixes:

A.UI Inconsistency fixes

1.20.0

Features:

1. External Study: Support to add your external studies and link them to projects. A new study type called external study has been introduced. This allows you to bring in any existing bucket in any other account apart from the Project account as a study even if the bucket was not provisioned via the Research Gateway interface (e.g., you can bring in existing data). External buckets can be linked to projects and mounted to work spaces in the project just like Project Storage.

2. Azure AD (Active Directory) Integration with Research Gateway.

Bug-fixes:

1.Internal study: If the study is created with root as a prefix, we can see behavior proper but if it is created with a specific prefix, we can see one empty file at the top after doing explore

2.Project Landing page: On load more button click, duplicate projects are shown.

3.Product-details page: On the refresh button click, send an event to the notification sink to get the latest product status.

4.Enterprise fix: If a user is a part of one OU (Organization Unit) has 1 project and has internal and external studies linked to it later, he is removed from that OU and added to new, Old OU Internal and External Studies should not be visible

5.On Org Card if one Org is attached to a single or multiple accounts the account id is not visible

6.In the project creation form if we click on the cost control enabled checkbox it deselects project storage check and vice versa

1.19.0

Features:
1.Ingress Gateway Project. This is a new project type that can be created against an account enabled for Secure Research Environments. This project is meant for researchers to be provided a storage area where they can upload files that they want to bring into a secure project. An Ingress Storage s3 product will be automatically created as part of project creation. The researchers can upload files via the UI and then submit an ingress request. After approval, these files are made available in the IngressStore folder that is mounted to their workspaces.

2.New additions to the catalog: JupyterLab and VS Code products. JupyterLab is a popular open-source software package that provides a highly extensible notebook authoring and editing environment. It offers advanced features and customization options compared to Jupyter Notebook. VS Code is a lightweight yet powerful open-source code editor on Linux. It provides built-in support for JavaScript, TypeScript, and Node.js, along with an extensive range of extensions for various languages and runtimes like C++, C#, Java, Python, PHP, Go, and .NET.

3.Integration with Egress application. With this integration, researchers will have an EgressStore folder automatically mounted to their workspaces. They can copy files that they want to extract from the SRE into this folder and submit an Egress Request. The request must be approved via the Egress Application and can be downloaded by the Information Governance lead after approvals.

4.Secure Research: Users will be able to add Secure Research Environment accounts and Secure Research Projects from the ‘Add Accounts’ and ‘Add Projects’ screens, provided they meet the preset requirements in their Organizational Unit (OU) and upon login.

5.Keypairs: Keypairs will be fetched based on the ProjectID.

6.Name Modification: Users will now encounter the term ‘Secure Research Environment’ instead of ‘Trusted Research Environment.’

7.RStudio product: The Authentication screen will be removed from the product.

8.Add project Screen: If all the required input parameters are not set, users will receive an error toaster message. For example, if a user tries to create a Secure Research Project or Data Library Project after creating a Secure Research Environment account without meeting all requirements, they will be restricted and see an error toaster message on the ‘Add Project’ screen.

9.Secure Research Linux product: Users should be able to view the ‘Instance Type’ action on the Product Details page for the Secure Research Linux product. Additionally, Load Balancers will be created during the Secure Research Project creation.

10.A confirmation dialog box will be displayed for the ‘stop’ action in the PCluster Product.

11.Enhanced Nice DCV product: Users can now view the ‘Instance Type’ action on the Product Details page for the Nice DCV product.

12.IGV-Viewer product: VPC and Subnet will no longer appear as input parameters in the product launch form.

13.Keyboard Accessibility fixes.

14.Security fixes.

Bug-fixes:

1.Internal Studies: When a user attempts to assign or create two studies with the same name for the same project, they shall receive an error toaster message.

2.Users can delink an account even if the account is linked to an internal study.

3.Assign product to project: If the stack is created twice during the assign action on the catalog page, duplicate products were being assigned to the project and were visible in the available products tab.

4.Events page: Users were unable to see the respective project name under the ‘project creation started’ event.

5.Project status: The ‘Active’ status for a project will now be updated after the completion of all steps.

6.Researcher login: If a user is assigned to an OU without a project, they should see an appropriate message on the Budgets screen.

7.When a user creates and deletes a project with an ALB (Application Load Balancer) simultaneously, it should not cause conflicts during the creation and deletion of the ALB.

8.Screen refresh count: The screen refresh count will be minimized during multiple project creation.

9.Storage creation issue: If a user unchecks the ‘Project Storage’ checkbox, selects an account in the project creation form, and clicks on the ‘Create Project’ action, the project will still be created with storage.

10.SAML Login: After successful authentication, users will be redirected to the home page without any issues.

1.18.0

Features:
1.Secure Research Linux Desktop. This product operates in a custom-created VPC with no internet access. It is accessed through a browser via a secure NICE DCV-based connection which provides access to a MATE desktop environment. It allows for Trusted Research environments to be created which are isolated from external access. The Secure Research Linux Desktop comes with a Chrome browser, docker engine, and miniconda pre-installed on the machine.

2.Encrypted S3 buckets. The S3 product in the standard catalog now allows for data to be encrypted using either an AWS-managed key or a customer-managed KMS key. This enables data at rest to be encrypted to meet security and regulatory needs.

3.Public studies can be mounted to workspaces. The studies available from the Registry of Open Data on AWS (RODA), can now be assigned to projects from the study details page. Once assigned to a project, the study appears in the Study Selection pane in the launch form for a researcher to select during the creation of a workspace. The selected study is then mounted to the workspace and can be used.

4.Internal studies can be created in read-write mode. This allows the PI to create studies that can be updated by researchers generating new data or when they want to share outputs with other researchers using the same study.

5. studies can be deleted.

6. labels are editable. This feature has been a long-standing customer request. The name of a project can now be edited and changed to suit the customer’s needs.

7.Support for SPAC in PCluster product. The user now has the option to install SPAC during the provisioning of a PCluster workspace. This provides an easy method to install other software like GROMACS or Open FOAM used in High-Performance Computing.

8.Subscription Renewal Date is enforced. Users can no longer log in beyond the subscription renewal date.

9.New IGV Viewer product in the catalog. IGV Viewer is an important open-source tool in genomics analysis and this was a demand from some of the customers who want to perform genomics analysis.

10.Updated NICE DCV standard catalog item. The NICE DCV product in the standard catalog has been updated with a newer version of the NICE DCV server. The workspace now comes with Chrome browser, docker engine, and miniconda pre-installed and the User interface uses the MATE desktop environment.

11.Keyboard accessibility improvements

12.Security improvements

Bug-fixes:

1.Admin: My Organizations: Organization Name Alignment issue.

2.In the login screen after entering a username and password and clicking on enter it is viewing the password, instead of logging in.

3.Create appropriate audit message and status for “delete setting” and “project storage terminate”.

4.Navigating from the Product launch form to the Create study section, if there is no Internal Study for the user, gives an error.

5.Error in updateBudgetForAccount.

6.Error in terminateProvisionedProduct - Provisioned product not found.

7.When the EBS product terminates getting the following error “This bucket is shared with other researchers, please check with them and disconnect any Sagemaker notebooks connected to it before terminating.” but there is no Sagemaker product in the project.

8.Error handling in login with an appropriate message. And add a logger during reset-password with the user name.

9.Added audit events for PROJECT_CREATION_STARTED and PROJECT_CREATION_COMPLETED.

10.In the PCluster product switch the Parameter Names based on the Scheduler type.

11.During project creation, if the S3 templates bucket is inaccessible, the user should see an error on the project events page.

12.On the Study s3 explore page, the “Actions” drop-down button should not be visible if the user selected one or more than one folder. Also, it should handle duplicate folder prefixes.

13.Project creation throws an error that the S3 bucket quota is reached even when the project storage requirement has been unchecked.

I4.n the Catalog page, if the stack creation fails, the existing product check mark should not be shown.

15.During Project Sync, Keypairs should be Inserted only if they have a valid project tag.

16.When a project is being deleted, all the keypairs for that project in the Research Gateway database should be deleted.

17.In the Catalog page, if we click “Assign product to project” twice, the stack is created twice. So duplicate products getting created.

18.During Project Creation, if multiple copies are created, Project Storage creation fails because of duplicate namespace values passed to the different stacks.

19.In the internal study, when I try to link compute resources and check assigned projects in study details, the same project name appears three times. It happens the same with unlinking as well.

20.In the Catalog page, show all existing tags in the dropdown.

21.Users with the Researcher role shall only be able to view studies that are assigned to the projects they are a part of.

22.Store created_on and updated_on in accounts collection. Add column “Last Updated” in the billing accounts table

23.If an Internal Study has no project assigned, we have to be able to delete it.

24.Upgrade Mongoose to 6.10.1

25.EC2-NICE-DCV: NiICE DCV-based products should be accessible through a one-time-usable URL.

26.Prevent users who are not assigned to any organization from performing any actions.

27.Notifications should be handled gracefully during post-provisioning when public IP is not found.

1.17.1

Bug-fixes:

1. Grouping organizations in the billing accounts screen.
   2.Provisioned Product: Card is not getting opened getting error while opening a failed provisioned product.
2. Admin login KPI card issue.

1.17.0

Enhancements:

1.Support for mounting Internal Studies to Sage maker instances. Users can now use the “Study selection” section of the Launch form, to select studies that should be mounted to Sage maker instances. The studies, so selected, will appear under the $HOME/studies folder.

2.New Billing Accounts screen - All accounts added to an organization will now be visible in the Billing Accounts screen to help the user track their overall spend in the AWS account. This screen shows the current AWS billing for that account (total across all regions including consumption from Research Gateway and externally). This screen also shows the forecast for the current month.

3.Bulk user tag updates. Importing users via CSV now has the capability to update tags for existing users. Tags have to follow the same constraints (maximum of 32 characters, maximum of 5 tags) and are updated in an all or none manner.

Bug-fixes:

1.Archived projects that had crossed the budget thresholds were reappearing as Stopped projects when Cost Control feature is on.

2.User edit function was not creating audit trail events.

3.Key pairs created in one project were appearing in another project if the associated account had more than one project linked to it.

4. user who is not assigned to any organization was getting incorrect message on logging in.

5.Search function in the catalog should show all products - assigned or unassigned.

1.16.0

Enhancements:
1.ec2 instances : Give user choice to attach external ebs volumes to ec2-instances.
2..Amazon EBS volume : Bring in EBS volume as a product in the catalog.
3.Project creation page---- add user form.
4.Admin: Budget Screen: able to see archived projects in organization also budget assigned is divided among archived projects as well.
5.User information should be editable.
6.Studies: Search action: enhancement: able to search studies with tag.
7.Pcluster : Give the user the choice to mount EBS volume to head node.
8.Keyboard accessibility : My Projects Page should be keyboard accessible.
9.Keyboard accessibility : Add Project button in My Project Page Should be keyboard accessible.
10.PI:Project Details Tab : Budget KPI cards Should be keyboard accessible.
11.11.Audit trail page : Select a value filter : items in the drop down should be sorted in alphabetical order.
12.12.Security: Upgrade xmldom npm package from 0.7.6 to 0.7.7 to fix critical vulnerability GHSA-crh6-fp67-6883.
13.NFR: Use distroless container images as the base images for Research Gateway.
14.Upgrade mongoose to 6.8.2 .

Bug-fixes:
1.CLONE - Audit Trail: OrgId should be added for each audit for all events.
2.Reduce API calls to ServiceCatalog in Daily Sync and manual sync process.
3.Alignment Issue: The project name is in top alignment with the logo but in the my products tab it was aligned as centered with logo.
4.Budgets Screen : provisioned products: created on is showing timing as utc it should show timing according to which region the user is logged in
5.fix the alignment issue for logo and name in product details page
6.UI Inconsistency : In the card level product type(amazon s3) in one color(#6387ff) but in the product details page product type color is different(#3E6BFF).
7.study search with tags bam,cram,MERS,SARS,fastq.
8.UI changes: In the landing page Breadcrumb and heading showing as "My projects" but when you click on the project there it is mentioned "All projects" in the breadcrumb.
9.SSH Window :User Name should be Shown white in color while typing.
10.UI Inconsistency: The Events tab under Project Details is paginated while that under Product Details has a Load More button.

1.15.0

Enhancements:

1. Principal Investigators will now see all the products launched by all the project team-members in the All Products tab. They will also be able to perform Stop and Terminate actions on the products using the 3-dotted icon which is available at the right side of the table.

   A.Products which are in Creating, Transitioning and Terminating State will not show any actions in the All Products tab.

   B.Products which are in stopped state will show only the Terminate action.

   C.Project Storage will not show any actions as it cannot be terminated independent of the project.

   D. EFS or FSx file-systems will only show the Terminate action.

2. PCluster Enhancement. Users will now be given choice to connect either an EFS or FSx file- system (provisioned earlier) to the PCluster.

3. End of Day (EOD) Report for Principal Investigators. EOD Reports will be sent with the subject as “Research Cost Tracking Daily Report”. It will show the following tables.

   A.Account table: This table lists all the accounts in use in your tenant. Each account will show the month-to-date consumption and the forecast value.

   B. Projects summary table: This table shows each project’s summary including month to date consumption and cumulative consumption (since inception).

   C. Project Details table: This table shows all the Active products per project and the month to date and cumulative cost per project. It also shows a single line item for the cumulative month-to-date and cumulative cost of Terminated products.
   4.For each provisioned product User will now be able to see Created on Parameter in Product Details Tab which will indicate the Product Creation Date.
   5.Audit Trail: Filter values should be sorted in Alphabetical order. This will help Users to find the expected values more easily.

Bug-fixes:

1.Amazon SageMaker : product launch failed. Note: User will need to manually sync their project once for the product template to get updated in their account.
2.Notificationsink: When send email of failed product fails, the error message talks about the email failure instead of actual error.
3.Date range picker on the Costs tab now allows to select only valid dates based on the lifespan of the product.
4.Choosing Organizational Unit should be disabled when the role is chosen as Admin while creating a user.
5.My Products tab: Budget value for product card is showing two decimal values but when the search is performed in my products tab it is not working as expected.
6.When a role gets removed from AWS console and we still have a setting in RG DB, new settings addition is failing by throwing a malformed policy error.
7.Product daily cost missing for certain days.
8.Even if the Status key value “DELETE_IN_PROGRESS” or “AVAILABLE” is set, the is Deleted flag is set to true..
9.User Creation: If B2C mode is set to true and the user is PI, then only create the default organization.
10.All audit events should be tagged with organization ID.

1.14.2

Enhancements :

Trigger Script from API : Clear the memory-cache which Node maintains on require file.
Rollback EOD report.

Bug-fixes :
Dates are getting duplicated in cost tab Chart and table.

1.14.1

Enhancements :

1.Add a route to call any script from config folder.

Bug-fixes:

1.Project Action : Product stop action is not working.
2.Email not sent if provisioned product is empty for any PI in the system.
3.Code-ql fixes.