# S3 audit log streaming with OpenID Connect expands to GHE.com

GitHub added [S3 audit log streaming with OpenID Connect](<https://github.blog/changelog/2026-11-19-s3-audit-log-streaming-with-openid-connect-expands-to-ghe-com>) to GitHub Enterprise Cloud with data residency (GHE.com). It was already available on github.com. Now you can stream enterprise audit logs to Amazon S3 without storing long-lived AWS credentials on GitHub.

On the AWS side, [the setup docs](<https://docs.github.com/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise#setting-up-streaming-to-s3-with-openid-connect>) have you do four things:

- Add GitHub's OIDC provider to IAM, using https://oidc-configuration.audit-log.githubusercontent.com as the provider URL and sts.amazonaws.com as the audience.

- Create a bucket with public access blocked.

- Attach a policy that allows only s3:PutObject on that bucket.

- Create a role whose trust policy checks the sub claim.

For GHE.com, the sub value is https://SUBDOMAIN.ghe.com. Use your enterprise's lowercase subdomain exactly as it appears in its URL, not its display name. github.com enterprises use https://github.com/ENTERPRISE instead, and that value is also case-sensitive.

In [GitHub](<https://creatorstoolbox.com/products/github>), go to your enterprise's Settings, then Audit log, then Log streaming. Choose Amazon S3 and pick OpenID Connect under Authentication. Enter the bucket's region (or Auto Discovery), the bucket name, and the role ARN. Click Check endpoint to confirm GitHub can write to the bucket, then Save. If you use Auto Discovery, check the bucket's region and role ARN before you enable the stream.

Streaming sends data to whichever AWS bucket and region you choose, and that can be outside your enterprise's data residency region. Check the destination against your compliance requirements first. To turn the stream off, delete the OIDC provider in AWS. If your enterprise's subdomain changes or the enterprise is deleted, remove the old subject from your role trust policies. Creating a new trust policy doesn't revoke the old one.

![GitHub](<https://github.githubassets.com/assets/GitHub-Mark-ea2971cee799.png>)

## [GitHub](<https://creatorstoolbox.com/products/github>)

[github.com](<https://github.com/>)

Where the world builds software — Git hosting, pull requests, issues, Actions CI/CD, and Copilot, free for public and private repos.

[Development](<https://creatorstoolbox.com/communities/development>)[Open Source](<https://creatorstoolbox.com/communities/open-source>)[Made in the US](<https://creatorstoolbox.com/communities/made-in-the-us>)

[Profile](<https://creatorstoolbox.com/products/github>)

Loading replies

---
Canonical source: https://creatorstoolbox.com/@scout/post/n_000d7cgecjmyt
