GCP API Gateway: Hands-on Technical Deep Dive

Discover api gateway, service control, service management, gcloud cli, and Google Cloud Console as the five components enabling management, authentication, monitoring, and logging of secure rest APIs.

Explore API gateway components, including API gateway, Service Control API, Service Management API, gcloud CLI, and Cloud Console, to define, deploy, monitor, and secure REST APIs on Google Cloud.

Download the lab files from the resources section and open them in Visual Studio Code on your local system. I will see you in the next video.

Install and verify Python, gcloud CLI, and pip on your system or use Cloud Shell to run CLI commands, then confirm versions with python --version, gcloud --version, and pip --version.

Set up a new project and configure the gcloud CLI to manage it from the command line, download lab files, and open them in Visual Studio Code.

Create a new project in the Google Cloud Console, copy the project number and ID for later use, and set up the gcloud CLI from your local system.

Authenticate the gcloud command line interface with gcloud auth login, list your gcp projects, set the active project by its project id, and verify it with gcloud config get project.

Enable essential Google Cloud services to deploy resources, including Compute Engine, DNS, Certificate Manager, Cloud Functions, Cloud Build, Artifact Registry, Cloud Run, API Gateway, Secrets Manager, and Service Control API.

Create service accounts for cloud functions to enable your APIs to call deployed code and perform tasks. Explore what service accounts and cloud functions are before proceeding.

Learn how service accounts authenticate workloads by attaching to resources like cloud functions, grant IAM roles, and access cloud storage buckets; understand user, default, and Google managed types.

Learn how Google Cloud Functions provide a serverless execution environment for single-purpose functions triggered by events or HTTP requests, and how to deploy them and use their URLs for APIs.

download the lab resources, open the Readme.txt, and create service accounts for cloud functions; open the files in Visual Studio Code on your local system.

Create three user-managed service accounts for cloud functions—customers, products, and purchase orders—using gcloud iam service accounts create, then list and view their project-specific service account emails.

Begin a hands-on lab by downloading the lab three deploy cloud functions files from resources, open them in Visual Studio Code, and prepare for the next video.

Explore the folder structure, open Readme.txt and requests.http, then examine the microservices folder with cloud functions for customers, products, and purchase orders to understand their roles.

Deploy and test cloud functions for get customer, get customers, get product, get products, and get purchase orders, returning matched items and the zone information from hard-coded data.

Download the lab files and open readme.txt, then replace the GCP project ID with your project ID from notes. Explore the CLI commands to see what they do.

Deploy a Gen2 cloud function with gcloud functions deploy in us-east1, unauthenticated access, entry point get_customers in get_customers_v1, python 3.11 runtime, source path, timeout, max instances, http trigger, service account.

Deploy five cloud functions in lab three: get customers v1, get customer v1, get products v1, get product v1, and get purchase orders v1, using the CLI and service accounts.

Review the diagram summarizing the current project state: five cloud functions, each linked to a service account, and verify functionality through testing.

Update the requests.http with your GCP project ID, then test five deployed cloud functions using the correct https URL format, via a browser or VS Code Rest client.

Create service accounts for the APIs in lab four, download the files from the resources section, open them in Visual Studio Code on your local system, and check readme.txt.

Create api service accounts for the essay products API, customers API, and purchase orders API using gcloud iam service accounts create, then list accounts to confirm eight total.

End lap four with cloud functions from lap three and three new service accounts for customers API, products API, and purchase orders API, awaiting workloads.

Create APIs, API configs, and gateways in this hands-on lab. Download the resources, open them in Visual Studio Code on your local system, and read the readme.txt.

Navigate the folder structure, review the readme and requests files, and examine the APIs folder to understand the customers, products, and purchase orders open API specs.

Walk through the open api specs for customers, products, and purchase orders, mapping get requests to cloud functions via x-google-backend and base paths in gcp api gateway.

Replace the GCP project ID in Readme.txt and in API specs (customers-v1-us-east-1.yaml, products-v1-us-east-1.yaml, and purchase orders), save all changes, and proceed to deployment.

Create api gateway APIs using the gcloud CLI, create customers, products, and purchase orders in lab five with async creation, then review the UI to see results.

Explore the GCP console to view three APIs: customers API, API products, and purchase orders, with their unique managed service IDs. Note that configs and gateways are not yet deployed.

Learn how API configs are created when uploading an API definition based on an open API spec, and how gateways host these configs to expose a scalable external URL.

Create API configs and gateways for customers, products, and purchase orders using gcloud API gateway commands, linking API configs to open API specs and backend service accounts asynchronously.

Explore api configs and gateways from the GCP console UI, view config files and their read-only yaml, and learn how gateway URLs expose customers, products, and purchase orders.

Demonstrates testing API gateway APIs from a client perspective by editing requests.http in VS Code, replacing the gateway URL hash, constructing requests, and verifying deployed APIs respond correctly.

Paste the gateway URL hash into a prepared text file to keep information handy, then review what we have in the project for future labs.

We have configured a gateway with a service account and API config exposing routes for customers, products, and purchase orders, each routing to corresponding v1 cloud functions.

Explore service-to-service communication by deploying version 2 of the purchase orders cloud function that calls get customers and get products via cloud function urls.

Walk through the get purchase orders v2 flow, deploying a GCP API gateway with cloud functions for customers and products, using the open API spec and v2 base path.

Replace the GCP project ID in readme.txt and purchase orders v2 us east one API spec with the real ID from the notes API gateway, save, and prepare for deployment.

Deploy secrets to store customer and product function URLs as environment variables for cloud functions. Create secrets with gcloud, choose replication policy, and grant secret accessor access via IAM.

Deploy the purchase orders v2 cloud function with gcloud functions deploy, specifying region, gen2, entry point, and trigger. Mount secrets for customers and products URLs; create API config and gateways.

Create an API config purchase orders v2 and a gateway, keeping v1 intact, redeploy the open API spec, and use the Purchase Orders API service account for authentication.

Explore the GCP API gateway for purchase orders v1 and v2, review their configs and gateways in the console, and test gateway access from Visual Studio Code.

Update the requests.http with the correct GCP project ID and gateway URL hash, then save. Test the cloud function and API gateway get purchase orders v2 to verify detailed responses.

Configure an api config for purchase orders v2 with base path, map get purchase orders to the v2 cloud function that calls get customers v1 and get products v1.

Explore service-to-service communication by calling a gateway URL and compare it to cloud function calls, noting initial similarities and evolving changes as you progress.

Walk through the code for a cloud function call to the customers gateway URL and products gateway URL, with the purchase orders-v3 base path and get purchase orders endpoint.

Review the get purchase orders v3 code and OpenAPI spec, update environment variables and gateway URLs, and replace the GCP project ID and gateway URL hash in prep for deployment.

Create secrets for get customers gateway URL us east one and get products gateway URL us east one, then deploy the purchase orders v3 cloud function and set up the api config and gateways.

Create the purchase orders v3 api config using the api spec at APIs/purchase orders/purchase orders v3 us east one.yaml with the bacon auth service account. Deploy gateway us east one.

Explore the GCP console to locate the Purchase Orders API gateway and its v3 config named purchase orders minus v three minus us east one.

Test the purchase orders v3 API via the API gateway by sending requests to the cloud function URL and validating v1–v3 endpoints in the UI, confirming all APIs work.

lab seven introduces the purchase orders v3 api config and gateway, routing to get purchase orders minus v3, and shows two service-to-service communication patterns using cloud functions and gateways.