Ona AWS Runner Failed: ROLLBACK_COMPLETE and ECS Circuit Breaker Errors

Share
Workaround available AWS Updated November 14, 2026How we research

Quick answer

Most AWS runner failures are network misconfiguration. Select a VPC, subnets across multiple AZs, and make sure outbound connectivity (IGW or NAT plus endpoints) exists.

Most likely fix: Fix stack parameters

How to fix it

Try these in order — the most common fix is first.

  1. 1. Fix stack parameters

    1. Select a VPC, at least one availability zone, and subnets in multiple AZs
    2. Redeploy the stack
    Did this fix it?
  2. 2. Fix connectivity

    1. Public subnets route to an Internet Gateway, private to a NAT Gateway
    2. Add VPC endpoints for Secrets Manager, S3 and ECR for private subnets
    3. Allow outbound HTTPS in security groups
    4. Force a new ECS deployment, then confirm Connected under Settings > Runners
    Did this fix it?

Symptoms

CloudFormation ends in ROLLBACK_COMPLETE, or the runner task shows CREATE_FAILED with ECS Deployment Circuit Breaker was triggered.

Why it happens

  • Missing or invalid VPC/subnet selections (parameter value for EC2RunnerInstancesSubnet does not exist)
  • No outbound connectivity: ResourceInitializationError
  • Private subnets lacking VPC endpoints for Secrets Manager, S3, ECR

This guide also covers

  • ona runner rollback_complete
  • ecs deployment circuit breaker gitpod
  • gitpod aws runner not working

Still not working?

If Gitpod keeps failing, you're not alone. See every Gitpod problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other Gitpod errors

All 10 Gitpod errors and fixes →