GitHub has extended OpenID Connect authentication for Amazon S3 audit-log streaming to GitHub Enterprise Cloud customers using its data-residency service, GHE.com. The company announced the change on November 19.
The feature was already available to enterprises using github.com. It allows administrators to export audit events to an S3 bucket without storing long-lived AWS access keys in GitHub.
The technical documentation identifies a configuration difference for data-residency customers. An AWS trust policy for a github.com enterprise uses a subject tied to the enterprise name. For GHE.com, the subject must instead match the enterprise subdomain, using a URL of the form https://SUBDOMAIN.ghe.com.
This is a concrete compatibility requirement, not a change in the underlying purpose of the log stream. The documentation also requires the administrator to verify the destination bucket and AWS role before enabling the stream.
GitHub warns that the chosen S3 destination may be outside the enterprise data-residency region. Enabling the new authentication method therefore does not by itself guarantee that exported audit data stays in the same region.
The company says streaming exports events from the point the feature is enabled. It uses at-least-once delivery, which means duplicate events are possible and downstream analysis may need to account for them.
GitHub has not announced a measured reduction in security incidents resulting from this expansion. The verified change concerns authentication and product availability.



















