Add support for API key and secret in STTOptions and SpeechStream #3039
Conversation
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
51750
force-pushed
the
aws-stt-credentia
branch
3 times, most recently
from
9547105 to
b58a519
Compare
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.
This PR adds support for hardcoded credentials in the AWS STT integration.
In #2297, api_key and api_secret were removed by @davidzhao to simplify the interface. While this improved usability, it also reduced flexibility. In certain cases—such as when environment variables or IAM roles are unavailable—users may still need to provide credentials manually.
This update restores that flexibility by reintroducing support for explicit credential configuration. It aligns with AWS best practices, which also allow manual credential setup when needed, while remaining compatible with existing authentication mechanisms.