An online media company is preparing to launch a live video transcoding service using Terraform to provision Compute Engine regional Managed Instance Groups (MIGs). The architecture requires scaling up to 400 N2 vCPUs in the us-central1 region during peak events. However, new GCP projects have a default regional vCPU quota well below this requirement. What architectural action should be taken prior to the initial production deployment to prevent provisioning failures?
- Request a regional vCPU quota increase in advance for the target region and wait for approval before executing the automated infrastructure provisioning.Answer
- BGrant the deployment pipeline service account the primitive Editor role so that it can bypass standard project quota restrictions.
- CConfigure the Terraform backend to store state files locally without object versioning to accelerate resource creation speed.
- DAssign the Service Account Admin role to the deployment pipeline service account to grant quota override permissions.
Answer
Request a regional vCPU quota increase in advance for the target region and wait for approval before executing the automated infrastructure provisioning.
Google Cloud enforces resource quotas on projects to prevent unexpected resource consumption and ensure cloud capacity. Default quotas for new projects are intentionally limited. To deploy large instance pools, cloud architects must submit quota increase requests in advance for the target region.
Step-by-Step Solution
Key Concept
Compute Engine Resource Quotas and Provisioning Prerequisites