Skip to main content
Environment classes define computing resources (instance type, disk size) for development environments.

Default classes

Class NameInstance TypeDisk SizeSpot Instance
SmallM6i Large (m6i.large)45 GBNo
RegularM6i XLarge (m6i.xlarge)80 GBNo
LargeM6i 2XLarge (m6i.2xlarge)100 GBNo
Extra LargeM6i 8XLarge (m6i.8xlarge)200 GBNo
Extra Large SpotM7i 8XLarge (m7i.8xlarge)200 GBYes
GPU LargeG5 4XLarge (g5.4xlarge)300 GBNo
GPU Large SpotG5 4XLarge (g5.4xlarge)300 GBYes

Create custom classes

  1. Go to Organization settings → Environment Classes (under AWS runners)
  2. Click Add Environment Class
  3. Configure:
    • Name and Description
    • Disk size: Storage capacity
    • Instance type: Any x64 EBS-enabled type (e.g., t3.medium, m5.large, c5.xlarge)
Environment class creation form showing name and description fields
Environment class creation form showing disk size and instance type configuration

Modify classes

Only name and description can be edited after creation. To change disk size or instance type, create a new class and optionally disable the old one.

Disable classes

When disabled:
  • Existing environments continue running
  • No new environments can use this class

Use classes

Select environment classes when creating environments manually or via project configuration.

Supported instance types

Requirements:
  • EBS volume support
  • X64 architecture (Intel or AMD)
Examples by category:
  • General purpose: t3.medium, t3.large, m5.large, m5.xlarge
  • Compute optimized: c5.large, c5.xlarge
  • Memory optimized: r5.large, r5.xlarge
  • Storage optimized: i3.large, d2.xlarge

Considerations

  • Regional availability: Not all types available in every region
  • Quotas: Ensure sufficient AWS account quota
  • Costs: Pricing varies by instance family
  • Instance generations: Newer generations offer better price-performance
  • Storage: Choose instances with more storage than RAM
See AWS EC2 Instance Types for details.

Best practices

  • Standardize classes across your organization
  • Limit to classes teams actually need
  • Create specialized classes for specific workloads (data processing, frontend, etc.)
  • Review usage patterns and adjust regularly