<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>github-enterprise on Field Notes</title><link>https://blog.penmen.net/tags/github-enterprise/</link><description>Recent content in github-enterprise on Field Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.penmen.net/tags/github-enterprise/index.xml" rel="self" type="application/rss+xml"/><item><title>CodeBuild-Hosted GitHub Actions Runners: From Static Egress to GHE Data Residency</title><link>https://blog.penmen.net/2026/06/codebuild-hosted-github-actions-runners-from-static-egress-to-ghe-data-residency/</link><pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.penmen.net/2026/06/codebuild-hosted-github-actions-runners-from-static-egress-to-ghe-data-residency/</guid><description>CodeBuild-hosted GitHub Actions runners in private subnets give you controlled, static egress through a NAT Gateway — meeting enterprise allowlisting requirements. This post covers two authentication paths: CodeConnections for github.com repos, and a PAT-based workaround for GitHub Enterprise Cloud with data residency (.ghe.com) where CodeConnections isn&amp;#39;t supported.</description></item></channel></rss>