Jimmy Ray

@tabern, the permissions are not the issue. The use of AWS Managed Policies is the issue. Some AWS customers do not use AWS Managed Policies because of the risk of...

@alicancakil In full transparency, I now work for AWS with the Amazon EKS team. While we haven't changed the need to use AWS Managed Policies for Amazon EKS, we have...

@willbeason The initial use case is that the audit activity was triggering the policy to call the external data provider every 60s. The external data provider was then making calls...

Sorting reports would be interesting, but I really wanted the control of background scans, like the interval, per policy. Some policies would have tighter intervals.

Undertstood. Feel free to scrap if it doesn't make sense to you. I think it makes sense for when a policy background scan may trigger a policy that makes calls...

So, what does that mean `now real time`? Can you link docs?

So, the point of my issue was a granular setting, to specify intervals per policy, giving more control over how often each policy scans. I guess that point is now...

This is similar to my [request](https://github.com/open-policy-agent/gatekeeper/issues/2055) With the addition of the external data provider, audit can cause calls to other applications, that could result in external calls to cloud APIs.

I just ran across this today, trying to get image verification working with Kyverno and Cosign. I wrote this [post](https://blog.jimmyray.io/kubernetes-workload-identity-with-aws-sdk-for-go-v2-927d2f258057) a few months ago to show how the AWS SDK...

Can we get this considered still? It is similar to Issue #2266.