# identity-aware proxy Published articles for identity-aware proxy. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## VPN Alternative for Internal Web Apps | Teleport DevFeed: [VPN Alternative for Internal Web Apps | Teleport]() Original publisher: [Read original article]() Author: info@goteleport.com (Sami Ali) Published: 2026-07-24T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [web applications](), [Virtual Private Network](), [Authorization](), [audit trail](), [Security]() Tags: [audit-trail](), [authorization](), [identity-aware-proxy](), [security](), [vpn](), [web](), [web-apps]() ### AI overview This guide explains why VPN-based access to internal web applications becomes difficult to manage as organizations grow. It presents an identity-aware proxy as an alternative that authenticates users to individual applications, enforces per-application authorization, and provides an audit trail tied to named identities. ### Source excerpt Replace VPN access to internal web apps with an identity-aware proxy: one login, one audit trail, and per-app access for every user. ## Hosting a fully Serverless Web-Based Postgres Admin Client on GCP using Pgweb, Cloud Run, & IAP DevFeed: [Hosting a fully Serverless Web-Based Postgres Admin Client on GCP using Pgweb, Cloud Run, & IAP]() Original publisher: [Read original article]() Author: Austen Novis Published: 2023-03-06T13:17:20Z Content type: tutorial Language: en Sources: [Engineering at Premise - Medium]() Topics: [Cloud Run](), [PostgreSQL](), [Google Cloud Platform (GCP)](), [Serverless](), [Authentication](), [Command-line interface](), [container]() Tags: [authentication](), [cli](), [cloud-computing](), [cloud-run](), [cloud-sql](), [cloudrun](), [container](), [deploy](), [gcp](), [google-cloud-platform](), [identity-aware-proxy](), [pgweb](), [postgresql](), [serverless](), [vpc]() ### AI overview A tutorial explains how to deploy Pgweb, a Go-based PostgreSQL administration client, as a serverless web application on Google Cloud. It uses Cloud Run, CloudSQL, a CloudSQL connector, Secret Manager, Artifact Registry, and optionally an HTTP load balancer with Identity-Aware Proxy for authentication. ### Source excerpt By Austen Novis, Staff Software Engineer Pgweb example screenshot There are a number of quality Postgres open source administration tools such as pgAdmin or DBeaver, but these tools require a persistent server to run. This means that each user needs to install the tool locally and setup their connections, or you need to host the tool in a cloud server, which can get expensive. A much cheaper alternative is to use Pgweb, a lightweight web-based database explorer for PostgreSQL written in Go, and deploy to Cloud Run. This allows you to utilize a web-based tool, for minimal cost, that can scale for any number of users. We will leverage several Google Cloud Platform services for the complete setup starting with a http load balancer to allow for a custom DNS name as well as enable Identity Aware Proxy (IAP), which is what we will be using for authentication. We will host the service in Cloud Run and connect directly to CloudSQL using a CloudSQL connector. You can bypass the load balancer and IAP if you would like to use username and passwords for authentication. Cloud componentsCloud Setup The first step is setting up your CloudSQL instance. This can be done via terraform or in the GCP console. The main requirement is that you enable a public ip address, which will allow us to use the CloudSQL Auth proxy to connect our Cloud Run instance to our CloudSQL instance. If this is not possible you can still connect to your CloudSQL instance to Cloud Run through a VPC Connector instead. Next we will need to save our database connection credentials in GCP's Secret Manger by creating a new secret called PGWEB_DATABASE_URL in the format of postgres:///DB_NAME?host=/cloudsql/PROJECT:REGION:INSTANCE_NAME&user=DB_USER&password=DB_PASSWORD . Now that we have our CloudSQL instance and connection secret we will deploy our Cloud Run instance using the gcloud cli. First we will need to push the desired Pgweb container to GCP's Artifact Registry, which we can do using the following commands ## Using Google-Managed Certificates and Identity-Aware Proxy With GKE DevFeed: [Using Google-Managed Certificates and Identity-Aware Proxy With GKE]() Original publisher: [Read original article]() Published: 2020-06-24T16:31:44Z Content type: tutorial Language: en Sources: [Brave New Geek]() Topics: [Google Cloud Platform (GCP)](), [Kubernetes](), [certificates](), [SSL](), [Authentication](), [Authorization](), [Deployment](), [Cloud]() Tags: [authentication](), [authorization](), [cloud](), [cloud-native](), [deployment](), [gclb](), [gcp](), [gke](), [google](), [google-cloud](), [identity-aware-proxy](), [ingress](), [kubernetes](), [load-balancer](), [proxy](), [security](), [ssl](), [tutorial](), [zero-trust]() ### AI overview A tutorial on deploying an application to Google Kubernetes Engine, configuring Google Cloud Load Balancer ingress with a global static IP and Google-managed SSL certificate, and enabling Identity-Aware Proxy for authenticated access. ### Source excerpt Ingress on Google Kubernetes Engine (GKE) uses a Google Cloud Load Balancer (GCLB). GCLB provides a single anycast IP that fronts all of your backend compute instances along with a lot of other rich features. In order to create a GCLB that uses HTTPS, an SSL certificate needs to be associated with the ingress resource. This certificate can either be self-managed or Google-managed. The benefit of using a Google-managed certificate is that they are provisioned, renewed, and managed for your domain names by Google. These managed certificates can also be configured directly with GKE, meaning we can configure our certificates the same way we declaratively configure our other Kubernetes resources such as deployments, services, and ingresses.