In Google, is there any easy way to configure a Storage-Bucket to base it’s access-permission decisions regarding the content inside of a Storage-Bucket upon the contents of a Web-Browser’s Cookies? I don’t really even know what the appropriate question to ask is, but SPECIFICALLY I know what I want to be able to either accept or refuse access to a set of static Web-Pages inside of a GCP Storage-Bucket based on a User’s Google Login.
When it comes to the contents served from a Storage Bucket. If I visit a URL, for instance rtdev.torello.directory (which is mapped to a GCP Storage-Bucket with the exact same name), is there any easy way to force the Storage-API Service or Cloud-Flare - to check if a User is logged into a particular Google-Account INSIDE OF HIS WEB-BROWSER before agreeing or refusing to serve static-pages from within a GCP Storage-Bucket? All I really want to do is to be able to be able to view content inside of my bucket, MYSELF by checking the Google-Credentials inside of a Web-Browser before granting access to the page. If the user requesting the page isn’t ME, I want to return some kind of ACESS-DENIED page to the user.
Is there some kind of Worker I can easily and quickly configure to do this? If it is some kind of involved project that is very difficult or expensive, please let me know.
My Domain is registered with Cloud-Flare, but currently I have a DNS Entry that just resolves to a GCP Bucket. I would like to be able to prevent anybody from accessing this DNS Entry, unless their Web-Browser is currently logged into a Google-Account - specifically - my own Google User-Name. Does anybody have any idea where I would even start to get the answer to this question. I have asked “Chat-GPT” but this time there was just to much jargon for me to have any idea what it was even talking about.