GitHub announced on November 19, 2026 that enterprise audit log streaming to Amazon S3 can use OpenID Connect on GitHub Enterprise Cloud with data residency, the service hosted under GHE.com. The option was already available on github.com. It lets the streaming service authenticate through a trusted identity provider and an AWS role, obtaining temporary credentials for its work. An enterprise can therefore remove a long-lived AWS access key from this part of its GitHub configuration. The release extends a specific authentication option for the existing log stream. Its value is in the routine work of keeping an evidence pipeline running. GitHub announcement
For a security team, a quiet logging integration is easy to overlook until a question needs the record. The credential may be owned by one team, the bucket by another and the search system by a third. A key rotation can expose that split when the records stop arriving. Replacing a durable secret with a bounded role session removes one piece of maintenance. It also makes the remaining dependencies more visible, including which enterprise can obtain the role, what the role can write and how the receiver detects a gap.
What moved to GHE.com#
GitHub Enterprise Cloud with data residency gives an enterprise a GHE.com subdomain and a specified hosting arrangement. The November update concerns customers using that route who send audit events to an S3 bucket. The S3 stream already has an access-key setup, and the documentation now describes OIDC as another authentication choice. A company can assess this change without redesigning the downstream tools that read its log objects. The important boundary is between GitHub’s authority to produce the events and AWS’s decision to allow those events to be written to a particular destination. GitHub streaming documentation
That destination is still chosen by the enterprise. GitHub’s setup guide specifically notes that streaming exports data to the AWS bucket and region selected, which may differ from the enterprise’s GitHub residency region. A procurement label about where the source is hosted is therefore only one part of the data path. The log archive, copies created by analytics and any retained search index have their own locations. For an operator tracing where an audit event went, it is useful to name those stages. A change in authentication can be made while the data’s route stays familiar, or as part of a wider change in where evidence is stored.
The audit log also has an audience beyond the person configuring it. An incident investigator may need to find who changed an organisation setting or when an identity’s access was altered. An administrator may want to check whether the stream itself was changed. The archive needs to be searchable on the terms the team uses in an investigation, and the investigation needs to know how far back the archive covers. This is why successful setup is an intermediate milestone. A stream is useful when its output can answer a question that crosses a period of normal operation and a period when something changed.
Consider a company whose engineering organisation uses GHE.com while its central security team runs an AWS account for records. The engineer who sets up the stream can arrange permission to write. The security team can independently arrange who reads the objects and how they enter its search tools. If the cloud role is narrowly tied to the publishing enterprise, the writer has a clear identity and purpose. If the archive has its own operational owner, someone can detect when that purpose stops being fulfilled. Both decisions are easier to sustain when they are recorded as properties of one integration rather than scattered in separate tickets.
Temporary credentials still need a durable trust decision#
In OIDC federation, a signed token presents claims from an identity provider. AWS’s Security Token Service can exchange a valid token for temporary credentials through AssumeRoleWithWebIdentity when a role’s trust conditions are met. The returned credentials carry the permissions assigned to the assumed role, subject to the applicable policies. That exchange changes how a service gains access. It allows the company to describe a recurring relationship and issue access for bounded sessions instead of storing a reusable AWS secret at the caller. The trust policy is the durable part of that relationship. AWS on requesting temporary credentials · Permissions for role sessions
The issuer matters because different workloads can use OIDC for different purposes. GitHub’s audit-log guide identifies the provider as oidc-configuration.audit-log.githubusercontent.com and the audience as sts.amazonaws.com. Its GHE.com instructions use a subject that matches the enterprise’s own subdomain. The guide also gives case-sensitive rules for the value. These details let the receiver check which particular relationship it is accepting. They belong to this audit stream and should be read from its documentation. A configuration copied from another GitHub workload can have a similar shape while referring to another issuer or subject. OIDC conditions for the audit stream
A trust rule answers who can obtain the role. A permissions rule answers what that role can do once obtained. GitHub’s example for the S3 writer grants s3:PutObject on objects in the designated bucket. The company receiving records separately controls who can list, read, query or delete them. That separation helps define the purpose of the writer. It can also make an incident easier to investigate because the identity that delivered an object is different from the one that later examined it. The actual authority still depends on every policy that applies to the request, including bucket policies and explicit denies. GitHub’s writer permissions · AWS policy evaluation for sessions
A short session and a small permission set work on different parts of exposure. A session expires, which limits the useful lifetime of those credentials. A permission set limits the operations they authorise while active. The process capable of obtaining another session still has to be managed, as does the trust rule that allows it. This is where the operational comparison belongs. A team can reduce the need to rotate a stored key while continuing to review the identity and permissions used by the integration. A system that issues temporary access can be stable for years, but its intended boundaries should stay understandable to the next operator.
Enterprise changes make those boundaries concrete. GitHub’s guide says that if a GHE.com subdomain changes, or the enterprise is deleted, the old subject should be removed from AWS trust policies. Creating a new policy does not revoke an old one. A migration can therefore succeed and leave an obsolete relationship behind. For a team splitting organisations or consolidating business units, the relevant record includes what was added and what was retired. The useful end state is that the receiver recognises the current publisher and can explain every relationship that remains active. GitHub’s subject lifecycle guidance
The test write begins the delivery check#
GitHub’s setup process includes checking the S3 endpoint before saving the stream. That verifies that GitHub can connect and write with the selected configuration at that time. A team can then look for ordinary events arriving at the destination and becoming available to the tool that will query them. Those are distinct stages. A writable bucket can have a broken downstream importer. A searchable index can contain old objects while nothing new arrives. Each check is more useful when it names the part of the pipeline it confirms and the time the evidence was obtained. GitHub’s endpoint check
An operator testing the transition can follow one known event through the path. A normal, authorised setting change can be identified in GitHub’s record, found in an object in the bucket and located through the search system. The team can compare the recorded event time with arrival and ingestion time. The point is to establish a baseline that can later distinguish a delay from a missing record. Choosing a routine event keeps the test close to the actual questions the pipeline is supposed to answer and avoids assuming that the endpoint test exercises every later stage.
It is also useful to track freshness over a quiet period. The absence of new objects can mean no relevant activity occurred or that the publisher could not write. A stream’s health signal and knowledge of expected activity can help distinguish the cases. The threshold for attention depends on the organisation’s working pattern and investigation needs. A worldwide company that changes settings throughout the day has a different pattern from a small group that does most administration once a week. The pipeline’s owner needs a way to detect a surprising silence that fits that pattern.
Moving authentication can make a gap more difficult to see if two methods overlap. During a staged migration, old and new objects can both appear valid. The downstream system needs to know what it is ingesting and how it identifies repeated events. The correct behaviour depends on its format and existing importer. An archive can retain both copies while a query system reconciles them. What matters in an investigation is that the operator can distinguish a duplicate from two similar actions and account for the interval in which the publishing configuration changed.
The event itself should remain recognisable as it moves. A permission change made in one organisation can resemble another change made a few seconds later in a different one. Combining only a name and approximate time can merge them accidentally. A search system that keeps the source identity, event details and arrival information has more evidence to separate the cases. A person doing an investigation can then ask whether a missing result is absent from the archive or merely hidden by the query. This is also useful when the same event arrives twice. A reliable explanation preserves the source record even when the presentation chooses to show only one instance.
The release announcement does not publish a new delivery guarantee or recovery benchmark. A team can therefore assess its own transition against what it needs to retain. If a temporary failure occurs, the operator wants to know what the source says about the stream, which records reached storage and whether downstream processing has caught up. Keeping those questions separate improves diagnosis. It can prevent an attempt to fix the identity configuration when the actual problem is a parser that no longer accepts a field in newly arriving records.
Storage location and record handling remain separate decisions#
GitHub explicitly asks users configuring S3 to check the destination bucket and region. The setting has consequences beyond network latency. An organisation may have made commitments about where employee or customer-related records are handled. Audit events can carry identity and organisational information even when the content of a repository is absent. The useful operational fact is the actual route to storage and search. Someone reviewing that route needs the region and account for the bucket as well as the systems that replicate, read and index it. GitHub’s destination guidance
Storage protection answers another question. Access control determines who can issue operations against the objects. Retention choices determine how long a record is kept and what can change it. Amazon S3 has Object Lock with governance and compliance modes, which apply different protections to object versions. Those are features of the destination. The OIDC authentication choice establishes how GitHub gets permission to write. An enterprise deciding whether to use retention controls can consider how long it needs the record, how it handles corrections and which accounts administer the archive. The answer depends on its evidence and records requirements. AWS Object Lock documentation
A log archive has its own access history. AWS documents CloudTrail support for S3 object data events such as reads, writes and deletes. Such data events are configured separately and can carry additional cost. They can help the operator identify what happened to objects after arrival. They also add another volume of records to manage. A scoped view of the operations relevant to the archive can be more useful than enabling a large collection nobody regularly queries. The choice depends on what the operator needs to prove about the handling of the evidence. S3 CloudTrail data events
The credentials exchanged with STS can also have an observable history. AWS describes CloudTrail events for federation and role sessions, giving a team a way to investigate the acquisition of access separately from actions in the bucket. That creates a useful diagnostic division. One failure can occur before access is granted, another after credentials are issued, and another when a consumer reads the object. The records are most helpful if the people responsible can connect those stages through time and the identity in use, with a clear explanation of what each trace can establish. AWS on logging IAM and STS
These extra records can have costs that differ from the stream itself. The number of objects, storage duration, read activity and search ingestion can all influence the bill. A migration to temporary credentials mainly changes access management. The organisation still needs to understand the cost of keeping and querying the resulting data. Watching the first normal billing period after a transition can show whether the new configuration sends the expected volume to the intended place or whether another copy is being stored and processed. This is part of maintaining a useful archive rather than just configuring a destination once.
Ownership is the part that survives the migration#
A service can cross several administrative boundaries with one authentication setting. The enterprise administrator knows the GitHub side, the identity team knows the trust relationship, the storage team owns the bucket and the response team knows how to investigate. An integration works more predictably when each can identify what they own and who notices a failure. That can be a small record beside the configuration, naming the source, destination, role and consumer. It lets a new operator follow the path without asking the people who originally copied the settings to reconstruct what they intended.
The same record helps with later changes. A new bucket policy can prevent writes. A trust policy can be tightened. The enterprise name can change. An analytics service can move to another account. Each may be a reasonable change in its own domain. Their combination can stop the log path. A known test event and a written description of the path let the owner verify the result after such a change. This approach deals with the integration as a working service that changes over time, including when nobody is formally migrating its authentication.
A fallback decision also needs a purpose. GitHub continues to document S3 access-key authentication alongside OIDC. A team deciding to retain or retire an old route can identify the circumstances under which it would use that route again, who can enable it and how it would account for the interval. A dormant credential left in a console may be hard to distinguish from a forgotten one. A retired credential with a clear plan for rebuilding access is easier to understand. Which choice suits the team depends on its capacity to diagnose and recover the service.
Retirement is clearer when tied to observed work. A team can establish which of the old credential's uses have moved and whether any unrelated job still depends on it. A key originally created for one integration may have acquired another use over time. Removing it can then reveal a dependency outside the audit stream. The right evidence is the inventory and recorded use available to the account owner, followed by verification of each intended replacement. This keeps a successful migration from turning into a surprise for another service. It also gives the team a more honest count of how many persistent secrets this particular change actually removed.
The maintenance benefit can be measured with ordinary work. Before the change, an operator might have spent time locating a key owner, scheduling a rotation and confirming that records resumed. Afterward, that work may shrink while the team spends more effort reviewing the relationship and changes to its boundaries. Tracking failed writes, unexplained gaps and time to restore a known-good stream shows whether the new arrangement is easier to operate. The source announcement establishes that the option exists. It leaves the effect on this particular company to the team operating it.
What would demonstrate the gain#
For a first rollout, a suitable success condition is that ordinary audit events keep reaching the chosen S3 destination and remain usable in investigation, with the intended enterprise and permissions represented in the trust relationship. A successful endpoint check supports that result at one instant. Following the event through storage and query supports it farther. Recording the transition interval, old relationships removed and current owners helps the result endure. A team can make the change incrementally when its existing controls and delivery checks support that approach.
An agreed baseline also helps when somebody asks whether the archive is late. The owner can compare the source event time, the time an object appeared and the time it became searchable. Those intervals vary for different reasons and need not have the same threshold. A team that needs recent activity during an incident can pay attention to the last stage as well as the first. A team mainly preserving records for later review may put more weight on completeness over a longer period. Measuring the path gives both teams a way to describe the service they have, and to notice when it changes.
The most important evidence after the first day is continuity through a later change. A role policy update or a downstream importer change should be reflected in the owner’s view of the service. If logs stop, the team should be able to locate the failing boundary using the records it normally has. Faster diagnosis, fewer unmanaged secrets and a clear destination are plausible gains from the new option. Each can be observed without assuming that switching authentication automatically makes the whole evidence chain reliable.
GHE.com’s new OIDC support removes a concrete reason to keep a long-lived AWS credential in GitHub for this task. It also offers a useful moment to follow the audit event end to end. The value reaches beyond the credential when the enterprise can show which publisher is authorised, where its records go and how the next operator will know if they stop. That is the operational result worth checking after the configuration has been saved.