-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove custom credentials chain to use default #2485
Conversation
Codecov ReportBase: 40.55% // Head: 40.60% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2485 +/- ##
==========================================
+ Coverage 40.55% 40.60% +0.04%
==========================================
Files 174 174
Lines 36259 36252 -7
==========================================
+ Hits 14706 14720 +14
+ Misses 20635 20615 -20
+ Partials 918 917 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
utils/awsutils/session.go
Outdated
@@ -46,6 +44,9 @@ func createDefaultSession(config *SessionConfig) (*session.Session, error) { | |||
} | |||
|
|||
func createCredentailsForRole(config *SessionConfig) (*credentials.Credentials, error) { | |||
if config.ExternalID == "" { | |||
return nil, errors.New("externalID is required fo IAM role") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: fo -> for
…rudderlabs/rudder-server into fix.aws-session-utils-use-default-chain
Description
OSS user reported that custom credentials chain is causing issues so removing to use default chain provided by SDK.
I have mistakenly configured AWS creds chain thinking about requirements from Kubernetes stand point and missed other types deployment like ECS so it is causing failures in ECS tasks when users want to task role instead of access keys from destination config. When no chain is mentioned default chain is taking care of this use case without any issues.
Notion Ticket
https://www.notion.so/rudderstacks/AWS-FTR-fix-OSS-issues-d64b93d9ed1d4c00a8d7e5573f7992c3
Security