Catch up with AWS changes #63
Merged
+136
−102
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
rjenkins
approved these changes
Oct 27, 2025
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 updates Rotel to the latest main version and resolves updates to the AWS credentials support. (Mostly renaming config -> creds).
The AWS Lambda environment handles most of the flexibility of AWS credentials by setting AWS environment variables with access keys and secure keys into the runtime. AFAIK, we don't need to handle the full flexibility of difference access profiles like in other runtimes. Therefore, we exclude building the default features of rotel that include the
aws_iamsupport. This reduces the deployment size for something we shouldn't need. We continue to include the Kafka support for now.