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
I have an EKS cluster and I want to create a SQS integration source on this. The docs suggest that I configure AWS secrets for auth purpose. However, my other pods actually use the service account based auth wherein EKS automounts a web identity token on my pod and then all AWS services use those by default.
How can I configure the IntegrationSource in a similar manner?
Thank you.
The text was updated successfully, but these errors were encountered:
The SQS client should expect to use session credentials then. This is useful in situation in which the user needs to assume an IAM role for doing operations in SQS.
Hi,
I have an EKS cluster and I want to create a SQS integration source on this. The docs suggest that I configure AWS secrets for auth purpose. However, my other pods actually use the service account based auth wherein EKS automounts a web identity token on my pod and then all AWS services use those by default.
How can I configure the
IntegrationSource
in a similar manner?Thank you.
The text was updated successfully, but these errors were encountered: