fix(s3): use AWS SDK default credential chain in standalone scripts and ingest util#1082
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ct3685
added a commit
that referenced
this pull request
May 20, 2026
## 🚀 Release: Staging to Production **Release Date:** 2026-05-20 ### Changes in this release - fix(s3): use AWS SDK default credential chain in standalone scripts and ingest util (#1082) (c35cf5e) --- *This PR is automatically created/updated when commits are pushed to staging.* *Merging this PR will trigger the release workflow to create a new GitHub release.* Co-authored-by: Cameron Taylor <50385537+ct3685@users.noreply.github.com>
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
1 participant
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.
Problem
Three more files had the same
?? ''S3 credential bug fixed in #1079 — passes empty strings when env vars are absent, breaking IAM/Copilot/ECS deployments.Files changed
packages-answers/scripts/generateCsv.tsnew S3with?? ''on both keyspackages-answers/scripts/initCsvRun.tsnew S3with?? ''on both keyspackages-answers/utils/src/ingest/document.tsnew S3Clientwith explicit credentials passed unconditionallyFix
Same pattern as #1079 — only attach
credentialswhen both env vars are non-empty; otherwise omit and let the AWS SDK default credential chain handle it (IAM, ECS task roles, Copilot, Render env vars, etc.).Test plan