The idea is:
Since I already have a service account running my cluster with access to specific types of secrets in AWS, it would be nice for n8n to be able to utilize that account for the external secrets connection to AWS and not have us need to make additional credentials where they aren’t needed.
My use case:
Using the external secrets like I do now, but with an account that already exists and runs n8n at the infra level
I think it would be beneficial to add this because:
Fewer accounts needed with access to our secrets
Any resources to support this?
Are you willing to work on this?
Don’t have the ability to.