GCP_API_Apigee

Conditions

Entity

capabilities

Mediation - provide the ability to catch and manipulate the request: Transformation, Security, Abuse detection, etc

API Analytics

API Runtime - handling runtime API trafic

Developer ecosystem

Private Cloud

Onprem DataCenter

GCP

Apigee Adapter for Envoy

Operational metrics

Api metrics

Business metrics

Api monitoring and alerting

Monetisation

Marketplace

API catalog

API life-cycle

Design

click to edit

Design

click to edit

OpenAPI - public framework to describe the contract

Environments

Publishing

API proxies and Shared Flow

Runtime tokens

Config

Organisation

An Apigee organization is associated with a single Google Cloud project

click to edit

An Apigee organization is the top-level entity for Apigee.

Users

An environment is a runtime execution context for your APIs.

managed by IAM

security, rate limiting, message transformation, or mediation within the request and response flows of your proxy.

Shared flow - - Shared flows can be used to combine a set of policies into a common pattern, allowing reuse of proxy logic in multiple APIs.

APIs are exposed on Apigee by implementing API proxies

Deployed to environment

click to edit

An organization might have three environments: development, test and production.

Users can be given different permissions in each environment. A developer might need full access in the development environment, but should have no write access in production.

Apigee organization admin has super user access within the organization.

Apps developer

Api Product

APPS

click to edit

Keys token

click to edit

. Apps present API keys, and OAuth tokens to access APIs. When an API key or OAuth token is verified in an API proxy,

click to edit

the app making the request is identified, as is the associated API product.

Env mapping

data collectors

KVM

Flow hooks are used to automatically attach shared flows to every proxy in an environment. This allows admins to enforce that security, logging, or other common policies are executed for all proxies.

Proxy

Conditional Flow

Post Flow

Preflow

Endpoint

Proxy Endpoint

Target Endpoint

Structure

Hostnames: {dev}.google.com

Environments: {dev}-order-system, {dev}-inventory

Env group: dev, test, prod

Proxy

GET https//api.testapi.com/orders/v1/carts/1234

proxy: orders-v1

proxy.pathsuffix = /carts/1234

env - prod-order system

click to edit

env group - prod: based on "api.testapi.com"

Conditions

click to edit

can chain with AND OR

should return TRUE or FALSE

IF statement

predefined vars can be useful

has operators

Java regex

MatchedPath

Matches - any string match

all case sensitive

Policies

Extension

Mediation

Security

Traffic management

Callout

Call a shared flow

Message logging

Java

OAuthV2

Basic Auth

JWT, SAML

HMAC

Verify ApiKey

CORS

click to edit

Cache response

click to edit

Enforse a reset quota

click to edit

Spike arrest

Data Capture

Preflow (always)

Step 1

Step 2

Conditional Flow 1

Step

Conditional Flow 2

Step

PostFlow (always)

Step

Route Rules

Route rules can enxicate, that we don't need the target endpoint

click to edit

After evaluating Proxy endpoint, Route rules are evaluated, to determine the target endpoint

First matching route rule indicates the target endpoint

Response returns via the same Proxy and Target endpoint

Target Server Specification