Support Pod Identity Controller associations for provider IAM permissions

[danielloader]

What problem are you facing?

I’d like to utilise pod identity controller associations to give my AWS providers the correct IAM privileges, instead of IRSA.

How could Official AWS Provider help solve your problem?

I’m not sure if it’s possible or not as the documentation doesn’t seem to indicate it is, if it is I’d love to see a sample ProviderConfig object for this authentication and authorisation mechanism.

[agjmills]

👍 for this. - of the supported values are below, None makes the most sense as it should fall back on AWS_CONTAINER_CREDENTIALS_FULL_URI and AWS_CONTAINER_AUTHORIZATION_TOKEN from the SDK, I think?

The ProviderConfig "aws-provider" is invalid: spec.credentials.source: Unsupported value: "yeet": supported values: "None", "Secret", "IRSA", "WebIdentity", "Upbound"

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[haarchri]

/fresh