From 2e4c26555c75750f642eae323a3be42276242797 Mon Sep 17 00:00:00 2001 From: Manas Srivastava Date: Wed, 29 Apr 2026 17:06:14 +0530 Subject: [PATCH] docs: mention BUILDKITE_S3_PROFILE in artifact upload help --- clicommand/artifact_upload.go | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/clicommand/artifact_upload.go b/clicommand/artifact_upload.go index f543ac4eb6..2771217252 100644 --- a/clicommand/artifact_upload.go +++ b/clicommand/artifact_upload.go @@ -44,6 +44,13 @@ You can use Amazon IAM assumed roles by specifying the session token: $ export BUILDKITE_S3_SESSION_TOKEN=zzz +To pick a named profile from your shared AWS config or credentials file +(~/.aws/config, ~/.aws/credentials), set BUILDKITE_S3_PROFILE. It takes +precedence over AWS_PROFILE, so you can override an AWS_PROFILE that the +agent's environment already has set for an unrelated purpose: + + $ export BUILDKITE_S3_PROFILE=name-of-your-aws-profile + Or upload directly to Google Cloud Storage: $ export BUILDKITE_GS_ACL=private