- It is critical that you configure any 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 to the public internet. For more information, see "Setting bucket and object access permissions" in the AWS Documentation.
- 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 AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at AWS Documentation.
Ensure your AWS access key ID and secret have the following permissions:
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 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.
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."