Private storage link

This page provides details on how to link and configure your private Amazon Web Services (AWS) Simple Storage Service (S3) storage to Buildkite Package Registries within your Buildkite organization. These processes can only be performed by Buildkite organization administrators.

By default, Buildkite Package Registries provides its own storage to house any packages, container images and modules stored in registries. You can also link your own private AWS S3 bucket to Buildkite Package Registries, which allows you to:

Manage Buildkite registry packages, container images and modules stored within your private AWS S3 bucket (that is, your private storage). Private storage:
- Located closer to your geographical location may provide faster registry access.
- Mitigates network transmission costs.
Use Buildkite Package Registries' management and metadata-handling features to manage these files in registries within your private storage.
Maintain control, ownership and sovereignty over the packages, container images and modules stored within your registries managed by Buildkite Package Registries.

Buildkite Package Registries uses AWS CloudFormation to provision its services within your private AWS S3 storage.

Before you start

Before you can start linking your private AWS S3 storage to Buildkite Package Registries, you will need to have created your own empty AWS S3 bucket.

Learn more about:

AWS S3 from the main Amazon S3 page, as well as the Amazon S3 documentation.
How to create an S3 bucket from the Amazon S3 documentation's Getting started guide.

Link your private storage to Buildkite Package Registries

To link your private AWS S3 storage to Buildkite Package Registries:

Select Settings in the global navigation to access the Organization Settings page.
In the Packages section, select Private Storage Link to open its page.
Select Add private storage link to begin configuring your private storage for Buildkite Package Registries.
On the Provide your storage's details page, in Step 2: Create or locate your AWS S3 bucket, select Open AWS to open the list of S3 buckets in your AWS account, to either retrieve your existing empty S3 bucket, or create a new one if you haven't already done so.

Note: If you are not already signed in to your AWS account, you may need to navigate to the area listing your S3 buckets.
Back on the Buildkite interface, in Step 3: Enter your AWS S3 bucket details, specify the Region (for example, us-east-1) and Bucket name for your AWS S3 bucket, then select Continue.
On the next Authorize Buildkite in AWS page, select Launch Stack to open the Quick create stack page in the AWS CloudFormation interface.
Ensure the the following fields are populated with the correct information:
- Template URL—should be based on:
  https://packages-public-assets.s3.amazonaws.com/cf-templates/byo-storage-bucket-policy-yyyymmdd.yml
- Stack name—buildkitePackagesProvisioning by default, but can be changed if another CloudFormation stack of the same name exists in your AWS account.
- BucketName—the name of your AWS S3 bucket (specified on the previous Provide your bucket's details page in Buildkite).
- KeyPrefix—{org.uuid}/, where {org.uuid} is the UUID of your Buildkite organization.
- IAM role - optional—specify any IAM role name or ARN to restrict the actions that can be performed on your CloudFormation stack in your S3 bucket.
Select Create stack to begin creating the CloudFormation stack for your S3 bucket.
Once the stack is created, return to the Buildkite interface and select Run diagnostic to verify that Buildkite Package Registries can publish (PUT), download (GET) and delete (DELETE) packages to and from your S3 private storage.
Once the Diagnostic Result page indicates a Pass for each of these three tests, select Create Private Storage Link complete this linking process.

You are returned to the Private Storage Link page, where you can:

Set the default Buildkite Package Registries storage

By default, your Buildkite organization uses storage provided by Buildkite (known as Buildkite-hosted storage).

The default storage is the storage used when a new registry is created.

Once you have configured at least one other private storage link, you can change the default storage to one of these configured private storage configurations. To do this:

Select Settings in the global navigation to access the Organization Settings page.
In the Packages section, select Private Storage Link to open its page.
Select Change to switch from using Buildkite-hosted storage (or a previously configured private storage beginning with s3://...) to your new private storage link. If this setting is currently configured to use a previously configured private storage link, the default storage can also be reverted back to using Buildkite-hosted storage.

All newly created registries will automatically use the default private storage location to house packages.