Creating a Project Space

Tenant administrators can create project spaces for users to access. Each project space is scoped to a specific AWS region.

To create a project space:

  1. On the Ansys Gateway powered by AWS home page, select New > Project space.

  2. Specify the project space settings:

    • Name your project space. This should be a meaningful name that will help users quickly find the project space and determine if it is suitable for their needs. For example, the name might indicate the intended purpose of the project space, key information about the types of resources it contains, or the intended user base.

    • Choose a region. The AWS region in which resources will be deployed.

    • Supported releases. Select the version of Ansys applications that you would like to use in this project space.

      • 2024 R2 and newer. These application versions can be installed on virtual desktops and autoscaling clusters.

        The operating systems supported in this project space are Windows Server 2019 and Rocky Linux 8.10 by CIQ.

      • 2024 R1 and older. These applications versions can be installed on virtual desktops and HPC clusters. If selected, the project space will also support the creation of file storage servers.

        The operating systems supported in this project space are Windows Server 2019 and AWS CentOS 7.9. An AWS CentOS 7.9 by Perforce image is also available but can only be used if you subscribed to that image on AWS Marketplace prior to December 17, 2024.

    • Tags. If required tags are displayed, specify their values. For example:

      Tag availability depends on whether Project space tags have been defined on the Administration > Tags page. For more information see Tags.

  3. In the Additional settings section, specify the default values for virtual desktop timers. Timers can be changed for individual virtual desktops after the virtual desktops are created.

    • Stop virtual desktop when no user has been signed in to the machine for. The maximum number of minutes that the virtual desktop can remain running when no user is signed in to the machine. (When a user connects to a virtual desktop, they are signed in to the machine so that they can use it.)

      This timer is activated when no users are listed on the Users tab in the virtual desktop details. When the user list has been empty for the specified period of time, the virtual machine is stopped.

      Note that users remain signed in to a virtual machine after disconnecting from a session unless the Sign out user who has been offline for timer is set.

    • Stop virtual desktop when no user has been connected to it for. The maximum number of minutes that the virtual desktop can remain running after all users have disconnected from it. (A user disconnects from the virtual desktop by closing their virtual desktop session.)

      This timer is activated when every user listed on the Users tab in the virtual desktop details has a status of 'Disconnected'. When the list has been in this state for the specified period of time, the virtual desktop is stopped.

    • Stop HPC cluster when CPU usage is below. Stops an HPC cluster when low CPU usage is detected. (This timer is only available in project spaces that support 2024 R1 or older releases.)

      First, define the threshold for low usage by specifying a percentage of CPU usage. Then, specify the shutdown interval by selecting the number of minutes after user low CPU usage detected.

    • Sign out user who has been offline for. Signs a user out of the virtual machine after a specified period of inactivity (plus an added 2 minutes of courtesy time provided by Windows).

    Note: A shutdown timer stops a Running resource, causing it to become Stopped. Resources in the Stopped state do not incur charges except for the underlying storage cost. Stopped resources can be started again.

  4. Click Create project space. The project space is created and is ready to be configured. For example:

Next steps: