wx44wx/pipecat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #4416 from pipecat-ai/mb/pr-4333-aws-credentials-review

Browse Source 
feat(aws): add shared credential resolver with boto3 chain fallback
This commit is contained in:
Mark Backman
2026-05-04 21:48:33 -04:00
committed by GitHub
parent 83190d38e9 678d40e102
commit fa31a2fd63
8 changed files with 311 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
changelog/4333.added.md Normal file
View File

@@ -0,0 +1 @@
- AWS Transcribe STT, Polly TTS, Bedrock LLM, and the Bedrock AgentCore processor now resolve credentials via the standard boto3 provider chain (EC2 instance profiles, EKS pod roles / IRSA, ECS task roles, SSO, `~/.aws/credentials`) when explicit credentials and `AWS_*` environment variables are absent. Services running with IAM roles no longer need to export static credentials.

1
changelog/4333.fixed.md Normal file
View File

@@ -0,0 +1 @@
- Fixed AWS Polly TTS, Bedrock LLM, and the Bedrock AgentCore processor erroring out when only one of `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` was set in the environment. The half-populated kwargs are no longer forwarded to aioboto3; partial env-var configurations now fall through to the boto3 credential chain like fully-unset configurations do.