Enabling GitHub Actions and configuring storage

External storage must be configured as part of enabling GitHub Actions on GitHub Enterprise Server.

Site administrators can enable GitHub Actions and configure enterprise settings.

In this article

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.

About 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.

GitHub Actions supports these storage providers:

  • Amazon S3
  • Azure Blob storage
  • S3-compatible MinIO Gateway for NAS

Amazon S3 permissions

If you use Amazon S3, GitHub Actions requires the following permissions for your AWS access key ID and secret:

  • s3:PutObject
  • s3:GetObject
  • s3:ListBucketMultipartUploads
  • s3:ListMultipartUploadParts
  • s3:AbortMultipartUpload
  • s3:DeleteObject

Enabling GitHub Actions

GitHub Actions support on GitHub Enterprise Server 2.22 is a limited public beta. Sign up for the beta.

Further reading

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.