Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Historically, we have used the
deploy
queue to manage resources in the production account. These agents run inside the account, and have fairly broad permissions that are used by several pipelines.Instead of relying on the agents to have the permissions we need, we can use an OIDC assumable role with custom permissions. The benefits being:
This pattern was recently used in the https://github.com/buildkite/site/pull/2898.
A new role has been created for
emojis
in https://github.com/buildkite/ops/pull/2149, that has permissions to interact with S3. However, we may need to tweak the permissions to add anything that's found to be missing for sync.The env var
ROLE_ACCOUNT_ID
has been added in the pipeline settings.Once the pipeline is working smoothly, we can remove buildkite/emojis from the allowlist on the deploy agents.