Note: GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. Review the external storage requirements below and sign up for the beta.
Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
To enable GitHub Actions on GitHub Enterprise Server, you must have access to external blob storage.
GitHub Actions uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of GitHub Actions. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.
GitHub Actions supports these storage providers:
- Azure Blob storage
- Amazon S3
- S3-compatible MinIO Gateway for NAS
Note: These are the only storage providers that GitHub supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. Contact us to request support for additional storage providers.
GitHub Actions requires the following permissions for the access key that will access the bucket:
GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. Sign up for the beta.
- "Hardware considerations" for your platform in "Setting up a GitHub Enterprise Server instance"