Skip to main content
Recipe PathThis guide corresponds to recipes/google-cloud.

What this integration does

The Google Cloud recipe extracts request context from the incoming HTTP request, calls Esper at POST /api/v1/runtime/mitigation, and either returns a mitigation response or forwards the request onward. Example shape:

Environment variables

  • ESPER_API_KEY
  • ESPER_API_URL

Deploy

Operational FitThis is the closest Google Cloud equivalent to the AWS Lambda recipe. It fits teams already running request handling at a serverless Google Cloud boundary and wanting Esper without introducing a separate always-on service.

Current behavior notes

  • Monitor is the safest place to start.
  • Challenge should return the Esper challenge payload or redirect URL from the runtime decision response.
  • Block should return an immediate deny response from the function boundary.