<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>cloud-run on It all begins with data</title>
    <link>https://www.beginswithdata.com/tags/cloud-run/</link>
    <description>Recent content in cloud-run on It all begins with data</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0100</lastBuildDate>
    
	<atom:link href="https://www.beginswithdata.com/tags/cloud-run/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Private GCS via Internal Load Balancers: No Client Auth Required</title>
      <link>https://www.beginswithdata.com/2026/09/22/private-gcs-via-ilb/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0100</pubDate>
      
      <guid>https://www.beginswithdata.com/2026/09/22/private-gcs-via-ilb/</guid>
      <description>For web serving use cases it&amp;rsquo;s common to put a load balancer in front of Cloud Storage providing a custom domain name with TLS, path flexibility with a URL map, and a single place to apply policy.
External Application Load Balancers (ALB) can use backend buckets that are shared publicly, or are kept private by granting a Google managed LB service account access. Many organizations use the private option to prevent direct API access to the bucket by unauthenticated users, as well as to avoid org policy exceptions for public access prevention and security findings that come with allUsers access.</description>
    </item>
    
  </channel>
</rss>