The request flow for WAAP with Cloud Armor, reCAPTCHA, and Apigee follows a fixed order:
- Client sends request: The client sends the request to the external Application Load Balancer with credentials such as a key, token, or certificate.
- Cloud Armor evaluates rules: Cloud Armor evaluates configured rules and policies; if a rule is violated, Cloud Armor rejects the request with an error message and status code.
- reCAPTCHA checks website traffic: For website calls, reCAPTCHA evaluates incoming traffic and adds risk scores; Cloud Armor can deny traffic that is not legitimate.
- Load balancer routes to Apigee: If there are no Cloud Armor rule violations, the load balancer routes the API request to Apigee.
- Apigee executes security policies: Apigee processes the request, executes security policies, allows or denies the request, and can route to different backends based on the client, the request, or both.
- Apigee forwards valid requests: Apigee forwards valid requests to GKE backends through internal IP addresses, to private data center backends through Cloud Interconnect, or to third-party services through Apigee NAT IP address provisioning.