Choosing compute resources

How do you configure compute resources for GitHub Actions?

How does it work?

Github-hosted runners provide 2 vCPU and 7 GiB memory by default. Larger runners are available up to 64 vCPU and 256 GB memory. But what do you do if you need a smaller or larger machine for your jobs?

With HyperEnv, you can choose from a wide variety of compute resource configurations. HyperEnv supports the following EC2 instance types:

  • t3.small - 2 vCPU, 2 GiB memory
  • t3.medium - 2 vCPU, 4 GiB memory
  • t3.large - 2 vCPU, 8 GiB memory
  • t3.xlarge - 4 vCPU, 16 GiB memory
  • t3.2xlarge - 8 vCPU, 32 GiB memory
  • m5.large - 2 vCPU, 8 GiB memory
  • m5.xlarge - 4 vCPU, 16 GiB memory
  • m5.2xlarge - 8 vCPU, 32 GiB memory
  • m5.4xlarge - 16 vCPU, 64 memory
  • m5.8xlarge - 32 vCPU, 128 GiB memory
  • m5.12xlarge - 48 vCPU, 192 GiB memory
  • m5.16xlarge - 64 vCPU, 256 GiB memory
  • m5.24xlarge - 96 vCPU, 384 GiB memory
Besides that, AWS offers more than 700 instance types, including virtual machines with GPUs and many more. In case you need a specific instance type, let us know.

Hosting GitHub runners on AWS has never been easier.

Get started Book a demo