Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing App Engine Firewall

cloudplatform.googleblog.com

Post reply on HN
Print view View original

31–35 of 35 posts

Re: Introducing App Engine Firewall

#31

Post by tadhunt »

not_that_noob wrote: post #8

Love it! I was thinking of migrating off GAE for this reason, but now will re-evaluate. One feature request - can we add a URL parameter to the firewall rule? The idea is I want to restrict access to certain URLs to a well-known set of IPs - e.g. I don't want login into admin pages unless coming from a known IP. Is this possible on GAE right now? I know I can split the service into two (restricted and public) and the…

We agree that this is an important use case, and is something we considered during the design. It is now supported by placing a Web Application Firewall in front of the App Engine application. We chose to limit the initial set of firewall features to IP address range blocking only — in part because that's sufficient to enable a WAF to front an App Engine Application.

-Tad Hunt (Manager on the App Engine team that brought you this firewall)

Re: Introducing App Engine Firewall

#33

Post by not_that_noob »

tadhunt wrote: post #31
not_that_noob wrote: post #8

Love it! I was thinking of migrating off GAE for this reason, but now will re-evaluate. One feature request - can we add a URL parameter to the firewall rule? The idea is I want to restrict access to certain URLs to a well-known set of IPs - e.g. I don't want login into admin pages unless coming from a known IP. Is this possible on GAE right now? I know I can split the service into two (restricted and public) and the…

We agree that this is an important use case, and is something we considered during the design. It is now supported by placing a Web Application Firewall in front of the App Engine application. We chose to limit the initial set of firewall features to IP address range blocking only — in part because that's sufficient to enable a WAF to front an App Engine Application. -Tad Hunt (Manager on the App Engine team that bro…

Got it - thanks. Any plans to add this as an integrated feature so we don't have to set up a separate WAF?

Re: Introducing App Engine Firewall

#34

Post by tadhunt »

not_that_noob wrote: post #33
tadhunt wrote: post #31

Earlier quoted context omitted.

We agree that this is an important use case, and is something we considered during the design. It is now supported by placing a Web Application Firewall in front of the App Engine application. We chose to limit the initial set of firewall features to IP address range blocking only — in part because that's sufficient to enable a WAF to front an App Engine Application. -Tad Hunt (Manager on the App Engine team that bro…

Got it - thanks. Any plans to add this as an integrated feature so we don't have to set up a separate WAF?

Feel free to reach out, my email is in my profile. We can discuss what you're looking for.

Re: Introducing App Engine Firewall

#35

Post by not_that_noob »

tadhunt wrote: post #34
not_that_noob wrote: post #33

Earlier quoted context omitted.

Got it - thanks. Any plans to add this as an integrated feature so we don't have to set up a separate WAF?

Feel free to reach out, my email is in my profile. We can discuss what you're looking for.

Would love to - couldn't find your email in your profile tho.

To keep the UI simple, I'd like to specify a URL and specify the IP range(s) that are allowed to access each. Bonus points if I can in addition to web UI submit and change the map programmatically. The first allows for greater security for admin pages and similar internal uses. The second allows us to provision for our enterprise users dynamically, who are at well known IPs.

Post reply on HN