Скачать или смотреть Route and secure multiple services with ngrok's Traffic Policy

When you need to expose multiple internal services to the internet, managing separate endpoints for each one becomes complex. Maintaining different public URLs, handling authentication across all of them, and routing requests to the right backends adds significant overhead.

In this video, Ishan shows off how to use ngrok's Traffic Policy engine to create a single entry point that intelligently routes traffic to multiple internal services based on request properties. You'll see how to use a wildcard cloud endpoint as a unified gateway, where the hostname determines which backend service receives the traffic—all configured through YAML.

🔗 RESOURCES

https://ngrok.com/docs/traffic-policy...

https://ngrok.com/docs/traffic-policy...
https://ngrok.com/docs/traffic-policy...
https://ngrok.com/docs/traffic-policy...

🚀 Get started: https://dashboard.ngrok.com/signup?ut...

🙋🏽COMMUNITY

🧑🏽‍💻 Join us on Discord:   / discord  
⭐️ Bluesky: https://bsky.app/profile/ngrok.com
🌐 Follow on 𝕏: https://x.com/ngrokHQ
🌐 Connect on LinkedIn:   / ngrok  

✨ Video tags - #ngrok #APIGateway #KubernetesOperator #loadbalancing #loadbalancer #loadbalance #azure #aws #gcp #k8s #cloudconnectivity #networkfailover #cloudnetwork

About ngrok:

ngrok is a globally distributed reverse proxy that secures, protects and accelerates your applications and network services, no matter where you run them. You can think of ngrok as the front door to your APIs and applications.
ngrok is a globally distributed reverse proxy that secures, protects and accelerates your applications and network services, no matter where you run them. You can think of ngrok as the front door to your APIs and applications.