Switch S3 deployment to OIDC authentication - #433
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates Cloud File Manager’s GitHub Actions deployment pipelines to authenticate to AWS via OIDC role assumption instead of long-lived static AWS access keys, and documents the new deployment/auth approach.
Changes:
- Updated S3 deployment workflows to use
aws-actions/configure-aws-credentialswith OIDC role assumption. - Removed usage of
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEYsecrets from deploy workflows. - Added/updated deployment documentation and references (README + new
doc/deploy.md).
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| readme.md | Adds a pointer to OIDC-based deployment setup and in-repo deployment docs. |
| doc/deploy.md | New deployment documentation describing branch/tag deploys and OIDC-based AWS access. |
| .github/workflows/ci.yml | Switches branch/tag S3 deploy job to OIDC-based AWS credentials. |
| .github/workflows/release-staging.yml | Switches staging promotion workflow to OIDC-based AWS credentials and adds run-name. |
| .github/workflows/release_production.yml | Switches production promotion workflow to OIDC-based AWS credentials and adds run-name. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Replace static AWS access-key secrets with OIDC role assumption in the S3 deploy workflows, per DEV-163. ci.yml s3-deploy plus release-staging.yml and release_production.yml (run-name added to both); doc/deploy.md + README reference added. Role ARN: arn:aws:iam::612297603577:role/cloud-file-manager Co-Authored-By: Claude <noreply@anthropic.com>
emcelroy
force-pushed
the
DEV-163-cloud-file-manager-oidc
branch
from
July 20, 2026 17:52
3ea2293 to
25d1187
Compare
emcelroy
marked this pull request as ready for review
July 20, 2026 17:59
scytacki
approved these changes
Jul 22, 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
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.
DEV-163
Replace static AWS access-key secrets with OIDC role assumption in the S3 deploy workflows, per DEV-163.
ci.ymls3-deploy plusrelease-staging.ymlandrelease_production.yml(run-name added to both);doc/deploy.md+READMEreference added.