Skip to content

docs: mention BUILDKITE_S3_PROFILE in artifact upload help #3869

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
moskyb merged 2 commits into from
May 5, 2026
Merged

docs: mention BUILDKITE_S3_PROFILE in artifact upload help #3869

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2e4c265
docs: mention BUILDKITE_S3_PROFILE in artifact upload help
mastermanas805 Apr 29, 2026
9c28968
Merge branch 'main' into fix/3636-document-s3-profile
mastermanas805 May 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions clicommand/artifact_upload.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,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
Expand Down