Failed to start EC2 instance in any availability zone. Errors: Failed to start EC2 instance with configuration 1 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2c). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2b.; Failed to start EC2 instance with configuration 2 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c.; Failed to start EC2 instance with configuration 3 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2c.

Error: Failed to start EC2 instance in any availability zone. Errors: Failed to start EC2 instance with configuration 1 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2c). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2b.; Failed to start EC2 instance with configuration 2 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c.; Failed to start EC2 instance with configuration 3 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2c.

All availability zone configurations failed

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: machulav/ec2-github-runner@v2.5.2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to start EC2 instance with configuration 3 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2c.

Failed to start EC2 instance with configuration 2 in region us-east-2: We currently do not have sufficient g4dn.xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get g4dn.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c.