- 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.
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 officially 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, 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 MinIO URL for your bucket's region.
Under "AWS S3 Bucket", type the name of the MinIO bucket you want to use to store package artifacts.
Under "AWS S3 Access Key", type your access key for MinIO.
Under "AWS S3 Secret Key", type your secret key for MinIO.
Under "AWS S3 Region", type your region for MinIO.
Under the left sidebar, click Save settings.
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."