HmC

  • Deployed System Connectivity

    Outbound Connectivity Systems deployed into a cloudspace in one of the local Hanscom clouds or commercial providers (e.g. AWS GovCloud, Azure, etc.) have the ability to reach out of the enclave to the greater network to access resources. Systems deployed in other DoD cloud providers (e.g. DISA m...
  • Logging in to HmC with a Certificate

    HmC uses certificate-based authentication only. There is no username/password access to HmC. Certificate options are: DoD Common Access Card (CAC) External Certificate Authority (ECA) certificate (more info about obtaining an ECA certificate (/kb/accounts/obtain-an-eca-certificate)) Logging in...
  • Source Code Accounts

    HmC provides built-in integrations with SoftwareForge (https://software.forge.mil) and DI2E (https://www.di2e.net/display/DI2E/DI2E+DevTools) for building and deploying Source Code assets that use SoftwareForge Subversion or DI2E.net Bitbucket (Stash) as a source code repository. This is done vi...
  • vGPU Capabilities

    Overview HmC has implemented virtual graphics processing unit (vGPU) capabilities to support select users that require additional resources for graphical or computational intensive applications. Availability At this time, the vGPU resources are in a separate cloudspace. If an organization need...
  • vGPU Optimization

    HmC has vGPU acceleration enabled across several Cloudspaces. If your Cloudspace offer vGPU, you will see operating systems with a [GPU] suffix. We continue to improve performance of our vGPU offering in each release and welcome any recommendations and comments to better support our users. Best ...