Skip to content
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

Jump to bottom

clarify supported bucket encryption #2269

Merged
merged 3 commits into from
Sep 4, 2023
Merged

clarify supported bucket encryption #2269

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8257d0a
clarify supported bucket encryption
pzeballos Jun 30, 2023
8e16712
Clarification on private log storage
pzeballos Aug 10, 2023
e4e6b6b
remove unnecessary blank line
pzeballos Sep 4, 2023
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
2 changes: 2 additions & 0 deletions pages/pipelines/managing_log_output.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,6 +157,8 @@ The folder structure and file format are as follows and are not customizable:
To set up a private build log archive storage:

1. Create an Amazon S3 bucket in *us-east-1* location (the only region that is currently supported).
>📘 SSE-S3 Encryption Support
> We don't support SSE-KMS encryption for customer log buckets, only SSE-S3.
pzeballos marked this conversation as resolved.
Show resolved Hide resolved
2. Provide *read* and *write* access permission policy for the Buildkite's AWS account `032379705303`.

Here's an example policy that contains an Amazon S3 bucket configuration with Buildkite's account number in it. Replace `my-bucket` and `my-prefix` placeholders with your Amazon S3 bucket information:
Expand Down