An alternative to AWS RES
AWS RES support ends on 30 September 2027
Keep your research on AWS, governed
AWS has ended development of Research and Engineering Studio (RES). Version 2026.09 is the final release, and AWS technical support and security updates stop on 30 September 2027. RosettaHub gives research teams what they relied on RES for, virtual desktops, HPC, shared data and single sign-on, with an AWS account and a budget for every project.
- AWS accounts governed
- 20,000+
- With universities and research institutions
- Since 2016
- Your AWS accounts governed, in every Region you use
- Any Region
- Multi-tenant, nothing to deploy, or a platform dedicated to your institution
- SaaS
AWS RES end of support: the dates
29 September 2026
Final release
AWS ended active development. Version 2026.09 is the last release of RES.
30 September 2027
End of AWS support
AWS technical support and security updates stop. RES stays open source and keeps running, but fixes become your team's job.
Before then
Choose your path
AWS describes four options: run RES yourself, have a partner run it, move to AWS managed services, or move to an alternative product.
From RES to RosettaHub, feature by feature
What your researchers use in RES today, and where they find it in RosettaHub. Everything below is in production, and the desktops, clusters and storage run in your own AWS accounts.
| What you use in RES | In RosettaHub |
|---|---|
| Linux and Windows virtual desktops | Linux and Windows desktops in the browser, started by the researcher |
| Notebooks and IDEs | Jupyter, RStudio and VS Code in one click |
| HPC | HPC clusters launched per project, with GPU instances where the project allows them |
| Software stacks | Custom images: any researcher can save an environment as an image and share it with a project, a group or other institutions |
| Project file systems | Shared file systems (Amazon EFS, Amazon FSx) per project, and a file browser to upload and download |
| Single sign-on | Your institution's single sign-on |
| SSH access | SSH to project machines without researchers handling keys |
| Projects and project roles | Project membership and roles managed by the principal investigator |
| Desktop sharing | Share a running session with a colleague |
| Desktop schedules and allowed instance types | Idle desktops stopped automatically or on a schedule; instance types allowed per project |
What RosettaHub adds for research institutions
An AWS account per project
Each project runs in its own AWS account, so isolation is clean and every cost belongs to one project, with no tagging to maintain.
Budgets that hold
A budget per project with the grant's own start date, tracked in near real time, AI included. At the limit, new activity stops and running machines are stopped with their data kept. Production services can be alert-only.
Budgets that move
Principal investigators move budget between projects themselves. Every transfer is logged, and unused budget carries over.
Collaborators from other institutions
A researcher can belong to several organisations at once, so partners join a project without new accounts. Share data, images and environments across projects and institutions.
Administration where it belongs
Institution, department, research group and project, each administered at its own level. Support staff can see exactly what a researcher sees.
Cost per grant
Exact cost per project from FOCUS 1.3 and CUR 2.0 data, kept in your own account, ready for grant reporting.
Policies per role and project
Regions, services, instance types and AI models per role, per user and per project, with continuous compliance against standards, implemented with Cloud Custodian.
Every route in
Web console, CLI, desktop app, OpenAPI, SDKs for Python, Java and JavaScript, and an MCP server for AI assistants.
SaaS, or dedicated to you
Multi-tenant SaaS, so there is no platform to deploy, patch or upgrade. If your institution needs its own, a dedicated platform is available.
Migrating from AWS RES, one project at a time
Start well before September 2027, and keep RES running until every project has moved.
-
1
Take stock
List your RES projects, users, software images, file systems and budgets.
-
2
Map and connect
Map each project to a RosettaHub project with its own AWS account and budget. Connect your single sign-on.
-
3
Bring images and data
Bring your software images across as custom images, and attach or copy the shared file systems.
-
4
Run one project in parallel
Move a first project and let its researchers work in both for a few weeks.
-
5
Move the rest
Move the remaining projects one at a time, each with its own budget from day one.
-
6
Retire RES
Switch RES off before AWS support ends on 30 September 2027.
Plan the move while RES is still supported
Book a call and we will look at your RES set-up with you and plan the first project.
Common questions
What is happening to Research and Engineering Studio on AWS?
AWS announced on 29 September 2026 that it has ended active development of Research and Engineering Studio (RES). Version 2026.09 is the final release. AWS technical support and security updates end on 30 September 2027. RES remains open-source under the Apache 2.0 licence and keeps running in your own AWS account, but after that date maintaining it is your responsibility.
What options does AWS describe?
AWS describes four paths: keep running RES yourself, have a partner run it, move to AWS managed services, or move to an alternative product. RosettaHub is an alternative that keeps your research environments on AWS, in your own accounts.
Is RosettaHub a drop-in replacement for RES?
No product is a drop-in replacement for RES. RosettaHub covers what researchers relied on RES for: Linux and Windows virtual desktops, software images, shared project storage, single sign-on and project roles. You move projects across one at a time, with RES running alongside until the last one has moved.
What happens if we keep running RES after 30 September 2027?
RES keeps running in your AWS account, but AWS no longer provides technical support or security updates. Patching, upgrades and fixes become the responsibility of your team or a partner.
Do we stay on AWS?
Yes. Your desktops, clusters, file systems and data run in your own AWS accounts, in the Regions you choose, at your own AWS rates. RosettaHub governs those accounts from its platform; your data stays where it is.
How long does a migration take?
It depends on the number of projects and software images. Most teams start with one project running in parallel, check it with its researchers, then move the others one at a time well before September 2027.
Can production research services be protected from budget stops?
Yes. Enforcement is chosen per project: experiments and sandboxes stop at their budget, while production services can be set to alert only.
Does RosettaHub support Windows desktops?
Yes. Researchers start Linux and Windows desktops in the browser, from your images or from images they have saved themselves.
Is RosettaHub an AWS Partner?
Yes. RosettaHub is an AWS Partner and has run research and teaching environments on AWS for universities and research institutions since 2016, governing more than 20,000 AWS accounts.