DCGW: CGW AI Gateway 2.0

## Jobs to be done (optional)

## Definition of done

- the API (when you create a new CGW configuration /cloud-gateway/configuration) will now have you specify type: ai or type: api, so DCGW API instructions that use this endpoint will all need an update
- Need to explain the architecture when you're using AIGW + API Gateway (do they share a network? need separate CPs, etc.)
- Roles: AIGW Admin, creator, etc. now have the CGW permissions baked in.

## Brain dump
- Properly make the connections on the AI Gateway landing page and docs that this is possible, sort of "how do you want to host your AI GW?"
- DCGW AI GW get started how to series or reference
- update that this is possible https://developer.konghq.com/serverless-gateways/ and https://developer.konghq.com/serverless-gateways/reference/
- users will need reassurance (benchmark numbers?) that DCGW can handle the large prompt sizes (including info on how we scale to accomodate)
- guidance on how they should structure their AIGW DCGW deployment (info on sharing networks with AIGW and KGW, how many networks? etc.)
- PII Sanitization (and all the AI add ons) from Reza: "This is where we get to the most value imho. And the details of how this will work - in 1) How it supports real use cases (e.g. what if I want a shared redis backend across geos) and 2) How 'seamless' the experience is will make the difference."
- Need to update https://developer.konghq.com/dedicated-cloud-gateways/reference/#dedicated-cloud-gateway-upgradeshttps://developer.konghq.com/dedicated-cloud-gateways/reference/#dedicated-cloud-gateway-upgrades as the policy will be different (DCGW team will own the version entirely)

## Open questions
- Will it just be AWS supported on release? (no Azure or GCP?)
- Can't set env var, is this just base RPS type env var or kong.conf type env var as well? Can we share the env var we did set so customers know what the baseline is?

## Information
DRP: Josh W.
Aha: https://konghq.aha.io/epics/CGW-E-52
PRD: https://docs.google.com/document/d/1_M_FSlAqSUvpa6ItoMa_VD0dunmgpg0UPYflzIsYf8Q/edit?tab=t.0#heading=h.7d3pxewom6nv
Jira project: https://home.atlassian.com/o/db2070d8-79a6-47bf-a620-cb316019f6bd/s/7f5e802c-4138-4a89-b52b-5eb3fb70d19e/project/KONGH-16/updates
demo: https://konghq.zoom.us/clips/share/-q73dJdlTiGF-lhi1x2fJw

## Due date (optional)

July 2026

## Size
L

Start with the linked PRD and Aha epic, then review the /cloud-gateway/configuration endpoint and the referenced Dedicated Cloud Gateways and serverless gateways pages. Define the documentation scope for AI Gateway hosting, networking, permissions, scaling, upgrades, and supported clouds. Done means the affected API instructions and reference pages explain the released behavior and resolve the listed open questions.

Written by the indexing model from the issue text.