AWS Research and Engineering Studio End of Support: What Happens After September 2027?

Is AWS RES shutting down?

No, not as a hosted cloud service being switched off. AWS is ending RES development and support, while existing deployments keep running in customers’ AWS accounts. RES remains available under the Apache 2.0 open-source license. The AWS RES end-of-support documentation explicitly separates continued operation from the end of AWS maintenance.

The practical change is who owns the software’s future: after EOSL, you or your chosen partner take responsibility for RES maintenance, security patching and further development. Continued operation does not establish that an unmaintained deployment is secure or suitable for your organization’s requirements.

AWS RES end-of-support timeline

Dates: AWS’s support milestones. Security-update boundary: AWS’s RES transition announcement.

What changes now?

AWS will release no new RES features, versions or enhancements. As of September 29, 2026, AWS no longer supports customers who begin using RES after that date. Existing customers retain support only while their installed release remains before its own EOSL. AWS still supplies critical-issue patches for releases within support, under the RES support policy.

Check your installed version before relying on the September 2027 deadline. That deadline belongs to 2026.09. For example, the support-policy table gives RES 2025.09 an EOSL of September 30, 2026. The live support-policy table and end-of-support documentation both confirm September 30, 2027 for 2026.09.

Moving to the final major release is also a separate deployment decision: the support policy allows in-place updates only between patch releases within the same major version. A new major version requires a new installation. This page does not claim to have tested that transition in a customer environment.

Can I still use AWS RES after September 30, 2027?

Yes. AWS confirms that existing deployments continue after EOSL. The open-source software remains available to run and maintain in your account. AWS does not announce deletion of deployments or an automatic loss of access on the final support date. Official continued-use FAQ

What ends is AWS’s RES technical support and fixes, including security updates. Your team or partner must own that work. The support policy already makes customers responsible for patching infrastructure and VDI hosts after deployment; this responsibility does not first begin in September 2027.

Who needs to take action?

The announcement affects organizations running RES, including research computing, engineering, HPC and virtual desktop environments that depend on its portal and AWS-provided RES support. It does not retire the underlying AWS services.

The following is ReplaceScout’s decision framework, based on AWS’s continued-use and transition options, rather than an AWS requirement that every customer migrate:

• An immediate migration may be unnecessary when the deployment is stable, an internal team can maintain RES and continued AWS vendor support is not required.
• Start planning before your release’s EOSL when you need vendor support or AWS security fixes, cannot maintain RES internally, operate a critical environment, or want a managed service.
• Evaluate partner maintenance when preserving custom RES workflows matters and you want someone else to own support and development. Confirm the actual service scope and contract with that partner.

AWS RES alternatives and migration options

AWS’s transition announcement names all the directions below. The workload column is a starting point for evaluation, not a product ranking or a claim of feature parity.

AWS explicitly says its managed-service paths are not drop-in replacements for RES. As an evaluation checklist, consider architecture, workflows, identity, desktops, storage, automation and operations that your deployment actually uses. Which of these must change depends on the destination and your environment; no universal compatibility or migration duration is established here.

AWS lists several partners supporting the transition and suggests contacting your AWS account team for an introduction. The blog identifies the partner descriptions as partner-provided. It does not establish a sole recommended provider. We have not independently benchmarked the alternative products, verified pricing, or performed a production migration.

Should you migrate now?

There is no announced requirement to migrate immediately. The final release has AWS support through September 30, 2027, and AWS says customers comfortable self-managing can continue operating RES. Earlier release deadlines still apply. AWS’s timing and customer guidance

Stay on RES temporarily if your team accepts the maintenance model and has an owner for it. Plan a migration if ongoing vendor support is required or a different architecture better meets your workload needs. Consider partner support if retaining RES is valuable but internal maintenance is impractical.

For critical environments, our recommendation is to evaluate and validate a path before the relevant support deadline rather than waiting until its last few weeks. Base timing on your own testing and change process. AWS’s announcement supplies no fixed six- or nine-month migration requirement, and this overview is not a production migration runbook.

What happens to other AWS services used by RES?

Only RES is covered by this announcement. Amazon EC2, Amazon Elastic File System (EFS), Amazon FSx and AWS Directory Service are unaffected. Amazon DCV continues to be developed and supported. RES’s EOSL does not automatically retire these services or the architecture built on them. AWS’s affected-services FAQ

Decide who will maintain your RES environment

The final AWS support date is September 30, 2027 for RES 2026.09. Existing deployments can continue afterward, with RES maintenance owned by you or a partner. Record your installed release, its support deadline and the owner of future security and support work; then evaluate migration if that ownership model does not meet your requirements.