CloudFormation says a IAM Role it just created does not exist

Question

Hi, a bunch of our stacks that did not change for a while are no longer working. It's like the dependencies between resources is no longer enforced, or else the IAM API experiences some delays.  
  
When creating a role and trying to reference to it in another resource (!Ref), it says the role does not exist.  The problematic role is pretty random, but it causes a rollback systematically.  
  
Those stacks templates were last updated over 2 months ago and they are just starting to fail now.  
  
Any idea?

Answer

Having the same issue here

Answer

I am inexplicably experiencing this as well. Searching shows that this typically happens when AWS APIs are experiencing increased latencies.  
  
I guess AWS doesn't know about it yet because it's not showing up in its status page.  
  
Burnt an entire morning on this, how annoying they don't know about an issue like this and can't report status on it for _hours_ after it started.

Answer

The AWS status page now shows a RESOLVED event for this.  Will try again.

CloudFormation says a IAM Role it just created does not exist

Contenus pertinents