Added support for instance profile credentials #101
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
Conflicts: nevado-jms/pom.xml
Conflicts: nevado-jms/pom.xml
…or secret are empty (null or empty string)
…s in certain cases. Prevents passed credentials from timing out.
…o add needed Jackson dependencies.
… dependency and add spring-context, which is needed.
…-sdk for jackson-dataformat-cbor due to conflict.
Release 1.3.2 oa7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I've made a small change to the SQS connector class to allow the use of instance profile credentials when no access keys are specified.
This improves security when an EC2 instance has a role that allows it to access the SQS and SNS services since access keys don't need to be stored anywhere.