src_0fd74b59b2db565a4c
- Source-provided label
- Not reported
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- May 05, 2025 14:08 UTC
- Retrieved
- Oct 08, 2026 03:45 UTC
Why Recreating an IAM Role Doesn't Restore Trust: A Gotcha in Role ARNs
In AWS, deleting and recreating an IAM role results in a new identity that breaks existing trust policies. This behavior improves security by preventing identity spoofing but can cause failures in cross-account access and third-party integrations if not properly understood.
Reference details
- Source category
- Research & news
- Report title
Why Recreating an IAM Role Doesn't Restore Trust: A Gotcha in Role ARNs- First reported
- May 05, 2025 14:08 UTC
- Last reported
- May 05, 2025 14:08 UTC
- Catalog updated
- Oct 08, 2026 03:45 UTC
- Record ID
56764c34e2a998d71f945796f2e9360836188e102ed350bc105e3c6a8a920da9
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 1 unverified.
Review source update dates and status
- src_0fd74b59b2db565a4cCollection status unverifiedLast successful batch: Unverified
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.