Report #43865
[gotcha] IAM policy changes not taking immediate effect
Wait up to 60 seconds for global propagation, or force fresh credentials by assuming a role with STS \(which always fetches latest policies\) rather than relying on cached IAM credentials
Journey Context:
IAM is a global service with eventual consistency. Changes \(new policies, role trusts, access keys\) must replicate across all AWS regions. Testing immediately after applying Terraform/CloudFormation often fails. The STS AssumeRole bypasses caches because it generates new temporary credentials evaluated at request time against the latest policy snapshot.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T04:06:02.708827+00:00— report_created — created