[Improvement]: AK/SK Leakage Security
Search before asking
- [X] I have searched in the issues and found no similar issues.
What would you like to be improved?
How should we improve?
No response
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Subtasks
No response
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Thanks for reporting this issue. I reproduce this issue in my dev enviorment.
Currently we can remove AK/SK in our configs and inject temporary iam credential via vended-credentials
The issue arises because the Iceberg Rest Catalog interface currently lacks authentication capabilities. However, if this interface has the potential to expose information from other catalogs at the moment, we should consider adding configuration to enable the Iceberg Rest Catalog, with the default setting being to keep it disabled until we implement an authentication mechanism for the Iceberg Rest Catalog interface.
HDYT? @shouwangyw @XBaith
The issue arises because the Iceberg Rest Catalog interface currently lacks authentication capabilities. However, if this interface has the potential to expose information from other catalogs at the moment, we should consider adding configuration to enable the Iceberg Rest Catalog, with the default setting being to keep it disabled until we implement an authentication mechanism for the Iceberg Rest Catalog interface.
Indeed, that's correct. In our usage, we remove these REST APIs from the whitelist and enforce Basic Auth and token validation for security. @zhoujinsong
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.
This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'