Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. The beta has ended. GitHub Actions is now generally available in GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes.
- For more information about upgrading to GitHub Enterprise Server 3.0 or later, see "Upgrading GitHub Enterprise Server."
- For more information about configuring GitHub Actions after you upgrade, see the documentation for GitHub Enterprise Server 3.0.
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.
Review hardware considerations
Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. If you're upgrading an existing GitHub Enterprise Server instance to 3.0 or later and want to configure GitHub Actions, note that the minimum hardware requirements have increased. For more information, see "Upgrading GitHub Enterprise Server."
If you configured the beta of GitHub Actions for the users of your GitHub Enterprise Server instance, you may need to provision additional CPU and memory resources. The additional resources you need to provision depend on the number of workflows your users run concurrently, and the overall levels of activity for your instance. For more information about monitoring the capacity and performance of GitHub Enterprise Server, see "Monitoring your appliance."
For more information about resource requirements for GitHub Enterprise Server, see the hardware considerations for your instance's platform.
For more information about adjusting resources for an existing instance, see "Increasing storage capacity" and "Increasing CPU or memory resources."
External storage requirements
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.
Amazon S3 permissions
GitHub Actions requires the following permissions for the access key that will access the bucket:
s3:PutObjects3:GetObjects3:ListBucketMultipartUploadss3:ListMultipartUploadPartss3:AbortMultipartUploads3:DeleteObjects3:ListBucket
Enabling GitHub Actions
GitHub Actions support on GitHub Enterprise Server 2.22 was available as a limited beta. To configure GitHub Actions for your instance, upgrade to GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes and "Upgrading GitHub Enterprise Server."
Further reading
- "Hardware considerations" for your platform in "Setting up a GitHub Enterprise Server instance"