Has anyone else's Vanta-AWS integration broken in the last 48 hours? Our monitoring started throwing "AccessDenied" errors on seemingly routine API calls, specifically around `securityhub:GetFindings` and `config:SelectAggregateResourceConfig`.
I suspect it's tied to AWS's recent rollout of more granular service control policies and IAM action updates. Our setup was working fine for months on the managed policy Vanta provided. The error trail points to new, more specific permissions being required.
What we're seeing:
* Intermittent failures in the Vanta dashboard for AWS resources, showing as "Unable to fetch data."
* Alerts for "Integration Health Degraded" citing IAM role issues.
* The Vanta `ReadOnly` policy we attached hasn't been updated in our repository since last year.
Before I start reverse-engineering their latest required actions, has anyone:
1. Already gotten a new policy JSON from support or updated their integration?
2. Identified the exact new API actions causing the `AccessDenied`?
3. Found a workaround besides granting broader `Read` permissions (which I'd like to avoid)?
I'm checking their docs now, but they don't seem to reflect any recent urgent changes. A community-shared policy snippet would save a lot of debugging time.