From what it appears, Cloudfront Path Pattern doesn't support complete regex.
What I want to achieve is to separate the requests /[a-z]* from the requests /[a-z]/.+ to different origins.
So, a request /page must have a different behavior from /page/something. And I can't seem to figure out a way of doing this.
On AWS, there is something called "Certificate Manager", that lets me procure valid TLS / SSL certificates for all my subdomains, that are issues by "Amazon" CA.
It takes care of upgradation, renewal, etc. without me having to interfere even a tiny bit.
I am looking for something similar on Google Cloud Platform, so that I don't have to first procure a certificate from a different CA.
As soon as I proceed to add a new origin for Google CDN distribution, it asks me to choose from load balancers (I would prefer not to create load balancer).
Ignoring the fact that I don't want to create a load balancer, I go ahead and create one on hopes that it would allow me to add my custom backend (an S3 bucket in this case), but even there it only allows me to add only "instance groups".
Is there any way at all that I could point this to a non-Google-Cloud origin?
On a decently loaded nginx/1.4.6 instance running on Ubuntu 16.04 LTS, sometimes the resources served are not getting expired. I always get "UPDATING" response instead of a "HIT" or a "MISS", which I would normally expect. This response with "UPDATING" header serves stale content, and is stuck there.
This had been fine for a long time; the only change that was recently implemented was that I recently configured letsencrypt-based encryption on my nginx instance.
Update: I'm also seeing logs that read like:
ignore long locked inactive cache entry 9b4d24d307449cfe263aab0ee53676c8
AWS Application Load Balancer ALBs support HTTP/2, and one would think we could switch over to these and immediately enjoy the benefits of HTTP/2.
Is there any possible a way to terminate HTTP/2 on ALB, so that the web servers don't need to be configured to support HTTP/2?