Enhanced Studio Pack on AWS

The Enhanced Studio Pack contains all the tools you need to do world-class development in a single, pre-configured environment. Use these instructions to deploy everything you need with the infrastructure required to support large projects, big files, and all your team members.

Helix Core Version Control

Helix Swarm Code Review

icon-products-hansoft-simple

Hansoft Project Management

Perforce Windows Workstations

Define Your AWS Environment

  1. To deploy your Enhanced Studio Pack on AWS, click on the template link (you should receive one after signing up).
  2. Create or log into your AWS account.
  3. In the template, you will see a list of parameters that define how your Perforce environment will be set up. Before you start editing parameters to create your stack, choose your region. By default US-East is selected. This template supports the following regions: us-east-1, us-east-2, us-west-1, us-west-2.
Define AWS Environment


We recommend selecting a region closest to your end users or a region that meets your compliance/security needs. Then define your parameters:

Stack Name

  1. Create a name following your organizations standard naming convention.
    If you don't have a standard convention, we recommend making the name easily recognizable. For example, perforce-${environment}-${team/department}
     
  2. If you deploy multiple instances Perforce Enhanced Studio Pack in the same region, create unique names for each. For example: production, team a, or team b. This will help you avoid an AWS duplication error: Stack [XYZ] already exists.

VPC Network Configuration

Your VPN contains all the network settings that give you access to use your Perforce software in the cloud.

  1. To start you must add at least one IP address. We recommend using the public IP address of the machine you are using to set up the stack in AWS.
  2. Replace 1.1.1.1 with your IPv4 address. Find your IP address >>
  3. /32 will remain unless there is a continuous block of IP addresses that need to be whitelisted. You can always add and delete IP addresses after you deploy.

Perforce Server Configuration

Define how you want the Helix Core server to be setup. Certain admin actions will require SSH access, for example operating system updates, Helix Core updates, reviewing logs, or expanding volume size. Daily use will not require SSH.

  1. To set up SSH, select an existing key or create a new one from your EC2 dashboard.
  2. The remaining fields in this section are optional. Once you are using the tool, you can adjust these at any time.
  3. If you know how much data you are using today, you may consider adjusting your Depot Volume Size to 1.5x your current data usage.

Virtualized Windows Workstation Configuration (Optional)

The virtual Windows workstation contains all the Perforce clients — Helix Sync, Helix Visual Client (P4V) — pre-configured. It also contains additional 3rd party tools and other powerful resources.

Instance size and your use of the software on the work station will influence the cost of the server needed to support it.

  1. To use a pre-configured Windows Workstation, select ‘True’
  2. Select Resources:
    • Instance type supported is EC2 G3 Instance Class. GPU prices will vary.
    • Root volume size is highly dependent on your use case. How much data will you check out? How much hard drive space do you want? How much data will be stored?  


Hansoft Configuration (Optional)

  1. To use the Perforce project management tool, select ‘True’
  2. Hansoft will be deployed to your AWS environment on its own server. We do not recommend adjusting resource defaults for initial setup.

Not sure you will use Hansoft right away? Deploy now and pause the Hansoft server until you are ready to start using. This will reduce your cloud operating costs.

Swarm Configuration (Optional)

  1. To use the Perforce code review tool, select ‘True’
  2. Swarm will be deployed to your AWS environment on its own server. We do not recommend adjusting resource defaults for initial setup.

Not sure you will use Swarm right away? Deploy now and pause the Swarm server until you are ready to start using. This will reduce your cloud operating costs.

Other Parameters

The Environment parameter is used in both resource naming and the tag on all resources.

Environment default is “prod.” We do not recommend changing this name. But it can be done if your needs require it.

Once you have defined all parameters, click Launch Your Instance. Estimate your monthly expense with the AWS calculator.

Connect to Your Windows Workstation

After you have completed deployment, you can connect to your Windows Workstation via NiceDVC browser, NiceDCV Client, or RDP. Review instructions below.

NiceDVC Browser

  1. To connect to your Windows Workstation via NiceDCV Browser, go to CloudFormation > Stacks > Parent Stack (Unique Name you Input). Click on the Outputs Tab.
    NiceDVC Browser
  2. Click on the PeforceWorkstationURL value.
     
  3. Enter your Perforce Workstation Credentials:
    Username: perforce
    Password: Value for PeforeceWorkstationInstanceID (located in the Outputs tab of the parent stack in CloudFormation)

NiceDVC Client

  1. Open NiceDCV Client.
     
  2. Enter the server you will connect to —value of the PerforceWorkstationPublicIP. Click Connect. Note: You can find the workstation server information on the Outputs tab of the Parent Stack in CloudFormation.
     
  3. Enter your Perforce Workstation Credentials.
    Username: perforce
    Password: Value for PeforeceWorkstationInstanceID (located in the Outputs tab of the parent stack in CloudFormation)

RDP

  1. Open your RDP tool of choice.
     
  2. Enter the server you will connect to – value of the PerforceWorkstationPublicIP. Click Connect. Note: You can find the workstation server information on the Outputs tab of the Parent Stack in CloudFormation.
     
  3. Enter your Perforce Workstation Credentials
    Username: perforce
    Password: Value for PeforeceWorkstationInstanceID (located in the Outputs tab of the parent stack in CloudFormation)

Access Helix Visual Client via Windows Workstation

When accessing your workstation for the first time, you need to complete your configuration.

  1. Once you are logged in, a powershell will display. This window will close when the configuration is complete.
    Powershell
  2. Authenticate your workstation. The password for the server is the value from the P4CommitInstanceID found in the CloudFormation Parent Stack Outputs tab.
    Helix Core Password
  3. Open Helix Visual Client (P4V) from the desktop icon. In the Open Connection dialog, leave the defaults. Click Okay.

Access Helix Sync via Windows Workstation

Helix Sync allows you to drop and drag assets to securely version any digital asset.

  1. Open the HelixSync desktop icon.
     
  2. In the dialog box, enter your server and username. This is the same information used for Helix Visual Client (P4V). No password is required since you’ve already authenticated the workstation.
     
  3. Get started with Helix Sync.

Connect to Helix Swarm via Windows Workstation

  1. Open Google Chrome.
     
  2. From the bookmarks area or bookmarks bar, click on Helix Swarm. The Helix Swarm login page will display.
     
  3. Enter your credentials:
    Username:  perforce
    Password: P4CommitInstanceID (located in the on CloudFormation Parent Stack Outputs tag

Connect to Hansoft via Windows Workstation

  1. Open connection instructions in Hansoft.txt file located on the workstation desktop.
     
  2. Open the Hansoft Client.
     
  3. Enter the Hansoft IP from the text file into the Hansoft server field of the Hansoft Client window.
     
  4. Enter the Hansoft Port into the Port field of the Hansoft Client window. Click Connect.

    NOTE: You may experience a time out error on your first attempt. Confirm the IP address and port are correct. Select continue. Trust the server and download any additional versions of Hansoft that may be available.
     
  5. Enter in your credentials:
    Username: Administrator
    Password: Hansoft EC2 Instance ID  (Listed as HansoftInstanceID located in the on CloudFormation Parent Stack Outputs tab)

Configure Perforce Products Without Windows Workstation

You can access your Perforce Software without the Windows Workstation.

  1. To connect to Helix Core via Perforce clients, Helix Swarm, or Hansoft you need to use a public IP. These are located in the CloudFormation Parent Stacks Outputs tab and are listed as:
    1. HansoftPublicIP
    2. P4CommitPublicIP
    3. SwarmPublicIP
       
  2. Download clients separately.
     
  3. Check out documentation to get started.

Update Firewall Rules to Allow Additional Users

If you have users who will connect Perforce from a different IP address than the one used to deploy, you will need to update your firewall rules to grant them access. 

  1. Follow AWS instructions on creating a security rule in your network security group.
     
  2. Input a rule for each user/IP address:
     
    1. Each user needs to provide you with their IP address in IPV4 format.
       
    2. The table below provides the port number for each product the user may need access to:
       
      ProductService TypePort Number
      Helix CoreTCP1666
      Helix SwarmHTTP80
      HansoftTCP52560
      Windows WorkstationTCP3389

Want Help Setting Up Perforce?

Contact our professional services team to talk to experts. They can optimize your Helix Core servers for top performance.

Launch Single Instance

Installing just Helix Core? 

Read More Docs

Get step-by-step instructions.