Does AWS offer something similar?
Introducing App Engine Firewall
11–20 of 35 posts
Re: Introducing App Engine Firewall
#12Love 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…
I too would love this. For now, we have add an auth layer to manage this and would love for that to not be necessary.
Re: Introducing App Engine Firewall
#13Does AWS offer something similar?
They have offered a more featureful product for a while: https://aws.amazon.com/waf/
That being said, the simplicity of this product is elegant and solves a lot of use cases without a lot of headache.
Re: Introducing App Engine Firewall
#14Does this work with the flexible environment too?
Re: Introducing App Engine Firewall
#15Does AWS offer something similar?
Azure too
Re: Introducing App Engine Firewall
#16This is a good feature. Wish app engine provides capability for blue-green deployments.
What do you mean? App Engine supports many versions of your application running simultaneously. You just deploy to a new version and migrate traffic (slowly or quickly, your choice).
Re: Introducing App Engine Firewall
#17Re: Introducing App Engine Firewall
#18This is a great first step. Reminds me of when Microsoft started shipping Windows with a firewall with XP.
Re: Introducing App Engine Firewall
#19My heart skipped a beat when I read the title as App Engine Farewell. Have been actively using App Engine since 2009 and the love it gets has been on a long downslide. Happy to see this feature come out though, the previous lightweight dos.yaml method was quite lacking.
Re: Introducing App Engine Firewall
#20I think this is a good product offering, and it's nice to see them compete with AWS on another front, as well as Digital Oceans' offering.
However, I wonder if these abstractions are detrimental to developers understanding the underlying technology? I'm not a supremely experienced developer but it takes very little effort to understand, for example, ufw and iptables on Linux distros.
Personally, though I'm (mostly) front end, I spend the majority of my time on the command line. My main editor is vim, I write bash scripts to do what I need instead of manually performing tasks, I often just use `cat` to write files instead of opening my editor, etc.
I found that managing things from the command line such as firewalls, daemons, and other tasks like managing databases, gave me deeper comprehension of what's going on. Are abstractions like this becoming crutches for tomorrows' developers?