Status Update
No update yet.
Comments
lu...@loblaw.ca
Most of the use cases I personally analyzed are not requiring a custom Cloud Run login. All we need is IAP to GCS integration. As long as the user is authenticated through IAP it should be able to access static assets in GCS in a "private way" and without making the GCS bucket public.
[Deleted User] <[Deleted User]>
ni...@noovle.com
I have setup GCS to host a static website, however, the website is accessible via both my custom domain (external HTTPS load balancer + SSL)
[1]
I have setup specific configurations on the backend bucket of the LB (Cloud Armor, CDN, ...), I would like to disable the storage.googleapis.com URL, as requests can simply bypass the route through the LB. I'm very interested on this feature to allow static websites to be hosted in private GCS buckets, which would prevent the objects from being accessible via the Storage API endpoint.
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
* Hosting a static website on a Cloud Storage but don't want to make publicly available the bucket
How this might work:
* Allowing only certain users to access the static website on a private bucket without using a Cloud Run login as proposed here [1].
If applicable, reasons why alternative solutions are not sufficient:
Based on this document [1] it is required to use Cloud Run login, the customers don't want to use Cloud Run in this case.
Documentation:
[1]