Error category

Cloud Platform Errors and Fixes

Troubleshoot cloud build, runtime, routing, IAM, container, and managed platform errors across compatible cloud infrastructure topics.

This Cloud Platforms troubleshooting hub collects real error signatures, quick fixes, common causes, and step-by-step debugging paths for developers who need a practical answer instead of a broad overview.

46 crawlable articles in this category. 58 additional records are indexed in JSON only (no standalone HTML route).

Browse Cloud Platforms records in the data catalog — search JSON index entries, including data-only records without standalone HTML guides.

Troubleshooting overview

Start by matching the exact error message, then check the technology, environment, credentials, network path, and deployment context. The pages below are grouped so you can move from broad Cloud Platforms symptoms to specific root-cause families without relying on client-side search.

Evidence labels are derived at build time from each Markdown record. Source-backed entries have public URLs under a Sources checked section, while partial-source entries expose public links without a complete source block.

Cloud Platforms diagnostic workflow

  1. Copy the exact error signature and compare it with the page title, code block, and technology label.
  2. Check whether the failure is local, CI-only, deployment-only, provider-side, or account-specific.
  3. Collect non-secret versions, configuration names, request IDs, and timestamps before making changes.
  4. Review source-backed or partial-source pages first when the issue might depend on provider behavior or version-specific bugs.
  5. Apply the smallest reversible fix and rerun the same failing action.

Common error types

  • permission denied
  • build failed
  • service unavailable
  • not found
  • timeout
  • configuration error

Common causes

  • EC2 SSH access failures remain top-tier developer pain point. With growing cloud adoption and many teams hitting this exact error, the commercial intent is strong. Access Denied validation confirmed at status.aws.amazon.com. (1 page)
  • Stack Overflow and HashiCorp discuss posts confirm this is a persistent issue across terraform + vault credential generation and AWS Lambda functions. Multiple root causes: expired IAM keys, stale environment variable conflicts between original session token and assume-role credentials, inactive access keys in IAM console. High commercial value for DevOps engineers managing cloud infra. (1 page)
  • AWS Lambda deployments fail with module-not-found when bundling tools (esbuild/webpack) omit or misplace dependencies. Enterprise cloud service with strong billing impact. Maps to Cloud Platforms. Not in covered-errors (Python SSL cert error is the only Python error listed, not Node.js lambda module issues). (1 page)
  • Cross-account S3-to-Lambda triggers consistently produce AccessDenied errors due to subtle bucket policy / IAM role gaps. Very high commercial value since Lambda+S3 is one of AWS's most-used serverless combos. Maps to Cloud Platforms. Not specifically covered in covered-errors.md which focuses on more basic cloud errors. (1 page)
  • Multiple AWS-related issues — AWS CDK issue aws/aws-cdk#37939 shows IAM propagation race condition for OpenSearchPolicy; many StackOverflow/GitHub issues show AccessDenied on S3 ListBucket in Lambda. These are classic timing-race issues affecting production deployments. Category: Cloud Platforms per mapping rules. (1 page)
  • AWS re:Post thread QUcSHvVHpkT8ad4EmspXORvA documents this exact scenario — AccessDeniedException when attempting to update Lambda function code via AWS CLI, despite having multiple permissions configured. Also corroborated by general security token troubleshooting guide. Category: Cloud Platforms. Medium-high commercial value as Lambda is heavily used in serverless production. (1 page)

Related technologies

  • AWS (19 pages)
  • GCP (3 pages)
  • Azure (3 pages)
  • Kubernetes (49 pages)
  • Vercel

Troubleshooting clusters

  • IAM and permission errors
  • Cloud build failures
  • Runtime and container errors
  • Network and DNS errors
  • Managed service routing errors
  • Environment configuration errors

Latest pages in this category

Representative source-backed errors

These entries include public source URLs in the imported page body. Use them first when you need evidence for provider behavior, SDK regressions, or version-specific failures.

Safe debugging checklist

  • Do not paste API keys, tokens, cookies, private repository snippets, or customer data into public issues.
  • Keep a rollback path before changing credentials, billing limits, DNS, CI secrets, or production deploy settings.
  • Prefer official documentation and source-backed entries over broad guesses when the error affects paid APIs or production deploys.

Top fixes

High-intent troubleshooting topics

  • how to fix Cloud Platforms errors
  • Cloud Platforms error fix
  • Cloud Platforms troubleshooting
  • Cloud Platforms authentication failed
  • Cloud Platforms timeout
  • Cloud Platforms permission denied
  • Cloud Platforms deployment failed
Cloud Platforms Google Gemini API

Google AI Studio Quota Exceeded Despite Paid Tier 1 — Free Tier Quota Bug

Fix quota exceeded error on paid Gemini API tier — developers have active billing and minimal usage but are stuck on free-tier quotas Includes evidence for Google Gemini API troubleshooting demand.

"Quota exceeded. Please try again later." on Google AI Studio despite being a paid Tier 1 project with minimal usage and active billing.
Cloud Platforms Azure

Azure Pipelines service connection authorization error AADSTS7000222 client secret expired

CI/CD pipelines fail with AADSTS7000222 when Azure AD service principal secrets expire; developers need to rotate credentials without breaking builds. Includes evidence for Azure troubleshooting demand.

AADSTS7000222: The provided client secret keys for app are expired — Azure DevOps pipeline fails to authenticate to Azure Resource Manager
Cloud Platforms GCP

GCP Cloud Build 403 Permission Denied custom service account deploy failure

Deployments from Google Cloud Build to Cloud Run fail with 403 Permission Denied when using custom service accounts; the roles required extend beyond just Cloud Build and Cloud Run. Includes evidence for GCP troubleshooting demand.

403 Permission Denied on Cloud Run Deploy / Cloud Build custom service account — even with Owner role
Cloud Platforms Azure

Long-running Azure Pipelines jobs lose authentication and fail at finalization

Azure Pipelines jobs that run longer than expected (e.g., compilation, testing suites) silently lose authentication mid-execution and fail at the finalization stage, requiring investigation of agent timeout and credential refresh settings. Includes evidence for Azure troubleshooting demand.

[BUG]: Long-running jobs lose authentication and fail at finalization — Azure Pipelines agent loses session token during extended execution
Cloud Platforms Kubernetes

Kubernetes CrashLoopBackOff with Empty Logs — Node Pressure Eviction Loop

Debug Kubernetes CrashLoopBackOff pod with empty logs, distinguish between application crashes vs node resource eviction (OOM/memory pressure) Includes evidence for Kubernetes troubleshooting demand.

CrashLoopBackOff | kubelet eviction node memory pressure/disk pressure | OOMKilled (Exit Code 137)
Cloud Platforms AWS

AWS Lambda Function Init Phase Timeout (Sandbox.Timedout)

Fix Lambda functions that timeout during the Init phase before Invoke can run; diagnose cold start delays, initialization code bottlenecks, or dependency loading issues Includes evidence for AWS troubleshooting demand.

Task timed out after 3.00 seconds — Lambda function times out during Init phase (Sandbox.Timedout)
Cloud Platforms Kubernetes

Kubernetes CrashLoopBackOff — OOMKilled (Exit Code 137) Diagnosis Guide

Diagnose and fix pods stuck in CrashLoopBackOff specifically caused by memory limits being exceeded (OOMKilled); determine whether to increase resources or fix memory leaks Includes evidence for Kubernetes troubleshooting demand.

CrashLoopBackOff with Reason: OOMKilled, Exit Code 137
Cloud Platforms Kubernetes

Kubernetes ImagePullBackOff ErrImagePull private registry credential failure

Troubleshoot Kubernetes pods stuck in ImagePullBackOff state due to private registry authentication failures or invalid image references Includes evidence for Kubernetes troubleshooting demand.

ImagePullBackOff / ErrImagePull — rpc error: code = Unknown desc = reading manifest latest in docker.io/alpinelinux/darkhttpdz: requested access to the resource is denied
Cloud Platforms Kubernetes

Kubernetes CrashLoopBackOff — Container Repeatedly Crashing After Startup in Production

Developer deploys to Kubernetes cluster and pods enter CrashLoopBackOff state. Needs systematic troubleshooting steps: kubectl logs, kubectl describe pod, checking CMD/ENTRYPOINT, verifying environment variables and service dependencies. Includes evidence for Kubernetes troubleshooting demand.

CrashLoopBackOff — pod starts, crashes, tries to restart again and repeats indefinitely
Cloud Platforms AWS

AWS Lambda Runtime Exited with signal: killed (OOMKill) — Max Memory Used Matches Memory Size

Lambda function hits memory ceiling, gets killed instantly with SIGKILL rather than graceful timeout; CloudWatch shows Max Memory Used equaling Memory Size — developer needs to find actual peak usage and set proper buffer Includes evidence for AWS troubleshooting demand.

Runtime exited with error: signal: killed — Max Memory Used matches Memory Size allocation exactly
Cloud Platforms Kubernetes

Kubernetes ImagePullBackOff — unable to pull container image from private registry

Fix Kubernetes ImagePullBackOff errors preventing pod startup due to image pull/auth/tag issues from container registries including Docker Hub rate limits. Includes evidence for Kubernetes troubleshooting demand.

ImagePullBackOff — kubelet: Failed to pull image — rpc error: code = Unknown desc = reading manifest latest requested access to the resource is denied
Cloud Platforms Kubernetes

Kubernetes ImagePullBackOff Container Image Pull Fails After ErrImagePull

Kubernetes pod stuck in ImagePullBackOff state; image wont pull from registry; developer needs to diagnose and fix image name typos, missing credentials, or Docker Hub rate limits Includes evidence for Kubernetes troubleshooting demand.

ImagePullBackOff - kubelet failed to pull container image after multiple ErrImagePull attempts; exponential backoff between retries
Cloud Platforms Kubernetes

Kubernetes Kubelet Fails with /dev/kmsg Operation Not Permitted on CI Runners

Bypass kubelet OOM watcher requiring /dev/kmsg access on restricted environments like GitHub Actions CI runners where /dev/kmsg is blocked by sandbox Includes evidence for Kubernetes troubleshooting demand.

Failed to run HollowKubelet: failed to create kubelet: open /dev/kmsg: operation not permitted
Cloud Platforms Kubernetes

Kubernetes Pod CrashLoopBackOff with OOMKilled — memory limit insufficient for Java workloads

DevOps engineer debugging Kubernetes pods repeatedly crashing with OutOfMemory killer; needs help configuring appropriate resource requests/limits and Java heap settings in containerized environment Includes evidence for Kubernetes troubleshooting demand.

Pod CrashLoopBackOff with last state terminated.reason=OOMKilled; Java application exceeding container memory limits set in Kubernetes deployment manifests
Cloud Platforms AWS

AWS Lambda AccessDenied — s3:ListBucket unauthorised due to IAM propagation race condition

Fix AWS Lambda getting AccessDenied on S3 ListBucket due to IAM role/permission propagation delays between CDK/Terraform deploy and Lambda execution Includes evidence for AWS troubleshooting demand.

AccessDenied: User: arn:aws:sts::XXXXX:assumed-role/YYY-role-ZZZ is not authorized to perform: s3:ListBucket on resource: arn:aws:s3:::bucket-name
Cloud Platforms Kubernetes / AWS ECR

EKS Kubernetes ImagePullBackOff caused by ECR registry authentication failure

Developer deploying to EKS on AWS gets ImagePullBackOff because kubelet cannot authenticate to private ECR registry; needs correct aws-iam-authenticator or IRSA setup for pod-to-ECR pulls Includes evidence for Kubernetes / AWS ECR troubleshooting demand.

ImagePullBackOff — Failed to pull image: rpc error: code = Unknown desc = failed to pull and unpack image: unauthorized: authentication required
Cloud Platforms AWS

AWS Lambda InvalidClientTokenId — IAM Access Key Authentication Failure

Fix AWS Lambda/CLI access key authentication errors (InvalidClientTokenId, ExpiredTokenException, SignatureDoesNotMatch) when using IAM credentials across AWS services Includes evidence for AWS troubleshooting demand.

InvalidClientTokenId: The security token included in the request is invalid

Browse all Cloud Platforms troubleshooting pages

Continue through the full static archive for this hub. Every listed page is crawlable and keeps its existing canonical URL.

Browse all Cloud Platforms troubleshooting pages