Environment classes

Environment classes define the specifications of your cloud development environments run by AWS runners. They control computing resources like instance type and disk size to meet your development needs.

​

Default environment classes

Gitpod comes with several pre-configured environment classes for your AWS runners. These defaults offer a range of computing resources to support different development workloads.

By default, Gitpod creates the following environment classes:

​

Creating custom environment classes

You can create custom environment classes tailored to your team’s specific requirements:

1. Navigate to your Gitpod organization settings
2. Select Environment Classes under AWS runners
3. Click Add Environment Class
4. Configure the following:
   • Name: A clear, descriptive identifier
   • Description: Details about the purpose or resources
   • Disk size: Storage capacity for the environment
   • Instance type: AWS EC2 instance type determining CPU and memory
     • Supports any x64 EBS-enabled instance type (e.g., t3.medium, m5.large, c5.xlarge)

​

Managing environment classes

​

Modifying environment classes

Once an environment class is created, only its name and description can be updated. To change configuration values like disk size or instance type, you must:

1. Create a new environment class with the desired specifications
2. Optionally disable the previous class

​

Disabling environment classes

When you disable an environment class:

• Existing environments using this class will continue to run
• Users cannot create new environments with this class
• Scheduled or automated processes cannot create new environments with this class

​

Using environment classes

Users can select environment classes when creating new development environments by:

• Manually selecting the environment class during environment creation
• Using a project that’s configured to use a specific environment class

​

Supported instance types

AWS runners support any instance type that meets the following requirements:

• Any EC2 instance with EBS volume support
• X64 architecture (Intel or AMD processors)

This gives you flexibility to choose from a wide range of compute options based on your development needs, including:

• 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

Select an instance type that aligns with your workload requirements for CPU, memory, and cost efficiency.

​

Considerations

• Regional availability: Not all instance types are available in every AWS region
• Quotas: Ensure your AWS account has sufficient quota for your chosen instance types
• Costs: Different instance families have varying pricing models
• Instance generations: Newer generations generally offer better price-performance ratio
• Storage: Use an instance type which has more storage than RAM.

For more information, see:

• AWS EC2 Instance Types
• Amazon EC2 Instance Type Families

​

Best practices

• Be prescriptive with your environment classes to standardize resources across your organization
• Limit the environment classes to what your teams actually need
• Create specialized classes for specific workloads (e.g., data processing, frontend development)
• Review usage patterns regularly and adjust available classes accordingly