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
feat: add support iam role support for warehouse destinations #2496
Conversation
Codecov ReportBase: 41.35% // Head: 41.47% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2496 +/- ##
==========================================
+ Coverage 41.35% 41.47% +0.11%
==========================================
Files 175 175
Lines 36266 36288 +22
==========================================
+ Hits 14998 15050 +52
+ Misses 20333 20303 -30
Partials 935 935
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. |
@koladilip can you provide additional details and context regarding the changes in this PR? |
@lvrach I have updated the issue description, let me know if you need more details are needed. |
…erlabs/rudder-server into feat.add-roles-support-for-redshift
Tested with redshift and glue, it is working fine. |
Co-authored-by: Francesco Casula <fracasula@users.noreply.github.com>
Co-authored-by: Francesco Casula <fracasula@users.noreply.github.com>
Description
As part of AWS FTR we need to support IAM roles instead of access keys for all AWS interactions. We already supported for file and streaming destinations using common utils. Now I am doing the same for warehouse destinations where there is dependency on S3 for Snowflake, deltalake, Redshift and using common utils we can automatically enable support for role based authentication.
In that process I have update glue client creation to use the same common utils to support role based auth.
Notion Ticket
https://www.notion.so/rudderstacks/AWS-FTR-for-Redshift-e7dc80ee847a49d6b7bb7fc03aeeffc2
Security