Use AWS OIDC in prod to push images to ECR#5784
Merged
yau-wd merged 2 commits intoFlowiseAI:mainfrom Feb 24, 2026
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
harshit-flowise
approved these changes
Feb 19, 2026
harshit-flowise
left a comment
harshit-flowise
left a comment
There was a problem hiding this comment.
Solid security improvement. Looks Good to me.
yau-wd
approved these changes
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Overview
Add Production-specific step to the "Docker Image CI - AWS ECR" GitHub workflow enabling use of AWS OIDC IAM role to push to AWS ECR.
The addition of the permission
id-token: writeis required per documentation, and the actionaws-actions/configure-aws-credentialswas pinned to version 6 via SHA1 to minimize supply chain attacks.