Job log archiving

How it works

When job log archiving is enabled, Buildkite Pipelines writes job logs to your specified S3 bucket instead of the default storage location. Each job's log output is stored as an object in your bucket. Buildkite Pipelines reads from this location when users view job logs in the Buildkite dashboard or through the API.

Configure private job log archiving

To configure job log archiving for your organization, you need to prepare an Amazon S3 bucket and then enable archiving in Buildkite.

Prepare your Amazon S3 bucket

• Read and understand Security best practices for Amazon S3.

• Your bucket must meet the following criteria:

  • Be located in Amazon's us-east-1 region.
  • Have a policy allowing cross-account read and write access from Buildkite's AWS account 032379705303.
  • Should implement modern S3 security features and configurations, such as (but not limited to):
    • Block public access to prevent accidental misconfiguration leading to data exposure.
    • ACLs disabled with bucket owner enforced to ensure your AWS account owns the objects written by Buildkite.
    • Server-side data encryption (SSE-S3 is enabled by default).
    • S3 Versioning to help recover objects from accidental deletion or overwrite.

• You may want to use Amazon S3 Lifecycle to manage storage class and object expiry.

Enable job log archiving

To enable job log archiving, contact Buildkite support at support@buildkite.com with your S3 bucket name and organization details. The support team will configure the archive location for your organization.

Related pages

• Build exports for exporting historical build data to your own storage.
• Managing log output for controlling how job logs are displayed.