Note: GitHub Packages is currently in beta for GitHub Enterprise Server 2.22. To join the beta for your instance, use the sign-up form.
About third-party storage for GitHub Packages
GitHub Packages on GitHub Enterprise Server uses external blob storage to store your packages. The amount of storage required depends on your usage of GitHub Packages.
At this time, GitHub Packages supports blob storage with Amazon Web Services (AWS) S3. MinIO is also supported, but configuration is not currently implemented in the GitHub Enterprise interface. You can use MinIO for storage by following the instructions for AWS S3, entering the analagous information for your MinIO configuration.
For the best experience, we recommend using a dedicated bucket for GitHub Packages, separate from the bucket you use for GitHub Actions storage.
Configuring AWS S3 as storage for GitHub Packages
Warning: Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using GitHub Packages.
Before you configure AWS as storage for GitHub Packages, make sure your AWS access key ID and secret have the following permissions:
s3:PutObjects3:GetObjects3:ListBucketMultipartUploadss3:ListMultipartUploadPartss3:AbortMultipartUploads3:DeleteObjects3:ListBucket
- From a GitHub Enterprise Server administrative account, click in the upper-right corner of any page.

- In the left sidebar, click Management Console.

- In the left sidebar, click Packages.

- Under "AWS Service URL", type the S3 endpoint URL for your bucket's region.

- Under "AWS S3 Bucket", type the name of the S3 bucket you want to use to store package artifacts.

- Under "AWS S3 Access Key", type your access key for S3.

- Under "AWS S3 Secret Key", type your secret key for S3.

- Under "AWS S3 Region", type your region for S3.

- Under the left sidebar, click Save settings.

- Wait for the configuration run to complete.