Migrate from AWS Research and Engineering Studio Support ends September 2027¶
AWS support for Research and Engineering Studio (RES) ends on 30 September 2027. Keep your research on AWS, governed.
What AWS announced¶
AWS has ended active development of Research and Engineering Studio on AWS. See AWS's announcement.
| Date | What happens |
|---|---|
| 29 September 2026 | Version 2026.09 is the final release |
| 30 September 2027 | AWS technical support and security updates end. RES stays open source (Apache 2.0) and keeps running in your account, but maintaining it becomes your responsibility |
AWS describes four paths: run 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.
From RES to RosettaHub, feature by feature¶
Everything below is in production today. The desktops, clusters and storage run in your own AWS accounts.
| What you use in RES | In RosettaHub |
|---|---|
| Linux and Windows virtual desktops | Virtual desktops in the browser, started by the researcher |
| Software stacks | Custom images: any researcher, not only an administrator, 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. See File Storage |
| HPC alongside desktops | HPC clusters launched per project, with GPU instances where the project allows them |
| Notebooks and IDEs | Jupyter, RStudio and VS Code in one click. See Jupyter Lab |
| Single sign-on | Your institution's identity provider. See Identity and Access |
| SSH access | SSH to project machines without researchers handling keys |
| Projects and project roles | Project membership and roles managed by the principal investigator. See Projects |
| Desktop sharing | Share a running session with a colleague. See Sharing |
| Desktop schedules and allowed instance types | Idle desktops stopped automatically or on a schedule; instance types allowed per project |
What RosettaHub adds¶
| An AWS account per project | Clean isolation, 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 wherever the service allows. Production services can be monitored only. See Budgets and Enforcement |
| Budgets that move | Principal investigators move budget between projects themselves; transfers are logged and unused budget carries over |
| Collaborators from other institutions | A researcher can belong to several organizations, so partners join a project without new accounts |
| Administration where it belongs | Institution, department, research group and project, each administered at its own level. See Organizations |
| Cost per grant | Exact cost per project from FOCUS 1.3 and CUR 2.0 data, kept in your own account. See Cost Allocation |
| Policies per role and project | Regions, services, instance types and AI models per role, user and project, with continuous compliance implemented with Cloud Custodian |
| Nothing to operate | Multi-tenant SaaS run by RosettaHub, or a platform dedicated to your institution |
Migrating, one project at a time¶
Start well before September 2027, and keep RES running until every project has moved.
- Take stock. List your RES projects, users, software images, file systems and budgets.
- Map and connect. Map each project to a RosettaHub project with its own AWS account and budget. Onboard your organization and connect your single sign-on.
- Bring images and data. Rebuild your software images as custom images, and attach or copy the shared file systems.
- Run one project in parallel. Move a first project and let its researchers work in both for a few weeks.
- Move the rest. Move the remaining projects one at a time, each with its own budget from day one.
- Retire RES. Switch RES off before AWS support ends on 30 September 2027.
Common questions¶
Is RosettaHub a drop-in replacement for RES?
No product is. RosettaHub covers what researchers relied on RES for, and 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.
Can production research services be protected from budget stops?
Yes. Enforcement is chosen per account: experiments and sandboxes stop at their budget, while production services can be monitored and alerted on without ever being stopped.