AWS HPC Blog

What’s next for Research and Engineering Studio on AWS

This post was contributed by Charlie Chuang, Madhu Vellakal, and Charunethran Panchalam Govindarajan.

Since launching Research and Engineering Studio on AWS (RES), we have helped customers stand up self-service portals for research, engineering, and technical computing on AWS. As this space has matured, with a strong ecosystem of AWS Partners and complementary AWS services, we are focusing our investment on managed services and partner-delivered solutions, and discontinuing development of RES. The 2026.09 release will be the final release. We are committed to making this transition smooth, and because RES is open source, it stays available to you.

What stays the same. RES is open-source software you deploy and run in your own AWS account, and that does not change. It remains available under the Apache 2.0 license, your existing deployment continues to operate, and you can keep running it as long as you want. We are also not changing the RES support policy: each release, including 2026.09, remains supported through its published End of Support Life (EOSL) date. After 2026.09 reaches its EOSL, AWS will no longer provide technical support or security updates for RES, but the software remains yours to run and maintain, or to have a partner maintain.

Your options

You have a few paths, and your AWS account team can help you choose and connect you with a partner:

  • Continue on RES yourself. RES is open-source software under the Apache 2.0 license that runs in your own AWS account. You can keep deploying, running, and updating it from the open-source project on your own. After 2026.09’s EOSL, you take on what AWS provided: maintenance, security patching, and any further development, but nothing stops working.
  • Continue on RES with a partner. An AWS Partner can take on what AWS did for you: ongoing support, maintenance, and security updates, and can continue to develop and customize RES for your environment. See Partners supporting the RES transition below, and contact your AWS account team for an introduction.
  • Move to an AWS managed service. If you would rather have a fully managed service, Amazon WorkSpaces and Amazon WorkSpaces Applications (formerly Amazon AppStream 2.0) provide managed virtual desktops, and AWS Parallel Computing Service (PCS) provides High-Performance Computing (HPC) cluster access through login nodes running Amazon DCV. None of these is a drop-in replacement for RES, so expect some change to your setup or workflows depending on the path you choose.
  • Move to an alternative product, such as NI-SP EF Portal, Engineering Development Hub (EDH), or Open OnDemand.

Partners supporting the RES transition

Several AWS Partners experienced with RES support customers through this transition. The descriptions below are provided by the partners. Contact your AWS account team for an introduction.

  • Do IT Now: Do IT Now is an AWS Partner with RES deployment and support experience, focused on manufacturing, automotive, aerospace, life sciences, and energy. For customers transitioning from RES, it provides advisory and transition support across all paths: continuing on RES, moving to an AWS managed service, or migrating to alternative architectures such as AWS PCS with Open OnDemand. Its team has supported active RES deployments. Do IT Now operates from Europe, the Middle East, and Africa (EMEA), Asia Pacific (APAC), and North America. Its RES services on AWS Marketplace are not currently listed publicly and are available through direct engagement with Do IT Now. To engage, contact info@doitnowgroup.com.
  • Itility: Itility is a technology consulting and engineering company across North America and EMEA, serving global semiconductor and photonics organizations through a distributed delivery model that combines local expertise with international scale, spanning cloud, software engineering, data and AI, platform engineering, and managed services. For customers transitioning from RES, Itility offers transition consulting, drawing on experience supporting multiple RES deployments. To learn more, contact Max.donkers@itility.nl.
  • Relevance Lab: Relevance Lab is an AWS Partner with a dedicated Research and Engineering Computing practice serving public sector organizations (higher education, healthcare, life sciences) and commercial organizations in areas such as EDA and aeronautics. For customers transitioning from RES, Relevance Lab offers its Research Gateway platform along with services covering deployment, migration, ongoing support, and continued development of open-source solutions. The team brings multi-year RES experience, including AWS GovCloud (US) and multi-account identity deployments, and operates across the US, UK, and APAC. Its RES transition services are planned to be available through AWS Marketplace (“RES Transition & Support”) from October 5, 2026. To learn more, contact anil.sriram@relevancelab.com.
  • The Server Labs: The Server Labs (TSL) is an AWS Partner with a dedicated HPC practice serving regulated industries, including Life Sciences & Healthcare, Space & Defense, Public Sector, Financial Services, and Critical Infrastructure environments. For customers moving on from RES, TSL provides managed services and continued development of its own supported RES build, with frontline support. The team has run customized RES environments in production. TSL is based in the UK and supports customers across EMEA. Its RES services will be available through AWS Marketplace as Research and Engineering Studio on AWS by The Server Labs (SKU: TSL-ULTRACOMPUTE-RES-DEPLOY / prod-qk2snyah7brl2). To engage and find out more, contact Tonie Odeniyi, Director of Growth and Strategic Partnerships, at tonie@theserverlabs.com.

Timing

  • September 29, 2026: 2026.09 is released as the final release. No new features or versions will follow. AWS Health Dashboard and email notifications go to RES customers, and RES is no longer promoted for new adoption.
  • Quarterly reminders: AWS Health Dashboard and email reminders to RES customers.
  • September 30, 2027: AWS support for RES ends. RES remains available as open source under Apache 2.0, and you can continue running it.

Affected customers. This affects customers running RES. If you want to remain on an AWS-supported or partner-supported footing, choose a path before 2026.09’s EOSL; your AWS account team and AWS partners can help. If you are comfortable self-managing the open-source project, no action is required. Your deployment keeps running.

Continued investment. We think RES customers are best served by a partner-led model going forward. AWS continues to invest in HPC and engineering workloads, including AWS PCS, alongside a growing partner ecosystem.

Conclusion

AWS is ending development of RES, but you have a clear path forward whichever direction fits your workload: continue on RES yourself or with a partner, move to an AWS managed service, or move to an alternative product. RES remains open source and keeps running in your account, so you can transition on your own timeline. For per-release support dates and your options, see the RES support policy and the RES documentation. To plan a transition or engage a partner, contact your AWS account team or AWS Support.

TAGS: , , , , ,
Charlie Chuang

Charlie Chuang

Charlie Chuang is a Senior Technical Product Manager for High Performance Computing at AWS, where he leads AWS ParallelCluster and works on AWS Parallel Computing Service (PCS). He works closely with research and engineering customers to run HPC and AI workloads reliably at scale. He guides the transition of Research and Engineering Studio (RES) to a partner-led model. Before AWS, he worked in semiconductor device-integration R&D at TSMC.

Charunethran Panchalam Govindarajan

Charunethran Panchalam Govindarajan

Charunethran Panchalam Govindarajan is a Sr. Product Marketing Manager at AWS, focused on High-Performance Computing and Quantum Technologies. He has worked across a broad range of technology domains, with a core interest in intersection of R&D and product development. Charunethran holds a Master's degree in Electrical Engineering from Stanford University. Outside of work, he enjoys sketching and philosophical conversations.

Madhu Vellakal

Madhu Vellakal

Madhu Vellakal is a Senior HPC Partner Solution Architect at AWS, where he focuses on scaling the impact of HPC partners in enabling customers and driving business outcomes. He holds an M.Eng from the University of Illinois Urbana-Champaign. With over 15 years of experience spanning HPC, Cloud, and AI, Madhu has authored 16 technical papers, co-authored book chapters, and served on numerous conference technical committees. Prior to AWS, he was a Senior Solution Architect at Rescale and a Research Programmer at the National Center for Supercomputing Applications at UIUC.