Skip to main content
Question

Recommended Developer Environment Architecture on AWS

  • August 3, 2026
  • 1 reply
  • 29 views

Praveen S

Implementing a mainframe modernization project using Rocket ED and Rocket ES on AWS. Target will run on RHEL.

 

ED v11has been installed on AWS Workspace for individual developers.

ES v11 has be installed on RHEL 9.8.

 

On the ED, developers are creating remote projects on ED installed on Single Shared Linux box where the code will be compiled and tested.

 

During development environment setup, we experienced challenges with remote compilation/builds from Enterprise Developer (on aws workspace) to a shared Linux environment. As a workaround, we provisioned dedicated EC2 instances for individual developers, with ED installed and configured on each developer server. This approach was also intended to provide isolated development workspaces and local Git repositories for concurrent development activities.

Would like to confirm:

  1. Whether provisioning a dedicated EC2 instance per developer is recommended/supported architecture for Rocket Enterprise Developer.
  2. Whether a shared Linux build environment is a supported and preferred approach, and if so, what configuration is required.
  3. Rocket's recommended best practices for:
    • Remote build/compile architecture
    • Multi-developer development environments on AWS

1 reply

Michael Bleistein
Forum|alt.badge.img+1

Hi Praveen,

Can you elaborate on this:

“During development environment setup, we experienced challenges with remote compilation/builds from Enterprise Developer (on aws workspace) to a shared Linux environment”

To your other questions:

  1. Yes, it is supported...really it is just a customer choice if they’re ok provisioning an EC 2 instance for each developer and each developer is licensed. Benefit is that it mostly alleviates any collision issues you run into in #2.
  2. Yes, it is supported. This was the original purpose behind remote projects….to add an IDE interface on to a multi-user compile/build architecture that has existed for a long time. Project setup and architecture + Permissions/Groups are important
  3. Potentially a very long answer and would need more information about the landscape of their application: Size, Number of source artifacts and types, files, Database, etc.