You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In AWS EKS pods and nodes can have an AWS IAM role attached that already contains the S3 permissions necessary. Is there a way to avoid having to pass S3 secret/key id or those are required right now?
The text was updated successfully, but these errors were encountered:
In AWS EKS pods and nodes can have an AWS IAM role attached that already contains the S3 permissions necessary. Is there a way to avoid having to pass S3 secret/key id or those are required right now?
The text was updated successfully, but these errors were encountered: