- It is critical that you set the restrictive access policies you need for your storage bucket, because GitHub does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
- We recommend using a dedicated bucket for GitHub Packages, separate from the bucket you use for GitHub Actions storage.
- 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 can enable and configure GitHub Packages on your GitHub Enterprise Server instance, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "Quickstart for configuring your MinIO storage bucket for GitHub Packages."
Ensure your MinIO external storage access key ID and secret have these permissions:
Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still supported by GitHub Packages on GitHub Enterprise. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details.
From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .
If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.
In the left sidebar, click Management Console.
In the left sidebar, click Packages.
Under "GitHub Packages", select Enable GitHub Packages.
Under "Packages Storage", select Amazon S3.
Enter your MinIO storage bucket's details in the AWS storage settings.
- AWS Service URL: The hosting URL for your MinIO bucket.
- AWS S3 Bucket: The name of your S3-compatible MinIO bucket dedicated to GitHub Packages.
- AWS S3 Access Key and AWS S3 Secret Key: Enter the MinIO access key ID and secret key to access your bucket.
Under the left sidebar, click Save settings.
Note: Saving settings in the Management Console restarts system services, which could result in user-visible downtime.
Wait for the configuration run to complete.
As a next step, you can customize which package ecosystems you would like to make available to end users on your GitHub Enterprise Server instance. For more information, see "Configuring package ecosystem support for your enterprise."
For an overview of getting started with GitHub Packages on GitHub, see "Getting started with GitHub Packages for your enterprise."