Google Cloud Central: Compute Engine incidents and maintenance

2501's Google Cloud Central specialty handles Compute Engine incidents and maintenance for a whole Google Cloud project from one central instance, under the IAM roles you grant it. It investigates, fixes and reports, only as far as you allow.

An instance stops answering, a service goes down, a disk fills up. The fix is usually small, but the cause can sit in the network, the instance or its permissions, and finding which often takes longer than the fix.

What 2501 does

The Google Cloud Central specialty takes these requests from your ticketing system and handles maintenance, incident investigation and remediation across Compute Engine and related services in its project. It works out why an instance cannot be reached, why a service is down, why an operation is refused for lack of a permission, or where infrastructure has drifted. When it cannot tell which resource a ticket means, it asks a person rather than guess. Where you allow it, it restarts a failed service, redeploys a resource, or clears or extends a full disk, working on the instance itself when that is where the fix is. It confirms the result before reporting what it changed and why.

You stay in control

• You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
• The IAM roles are the hard limit: an agent granted only read access cannot delete an instance, whatever a ticket says.
• Your rules decide which resources are in scope, and destructive commands can be blacklisted outright.
• On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Do we register every instance with 2501? No. One agent works from a central instance and handles the project from there.

Does it work beyond Compute Engine? It covers Compute Engine and the services related to it, in one project. Other Google Cloud services are outside this specialty.

Related

• Guardrails: what an agent may never touch
• AWS Central: EC2 incidents and maintenance, investigated and fixed
• Azure Central: incidents and maintenance on Azure VMs
• Terraform Operator: Terraform and OpenTofu plans, drift and state