title: How to get CloudFormation to respect Kinesis simultaneous stream creation limits
body: <p>I have a CloudFormation stack that contains multiple Kinesis streams.  If the stream count is less than 5 during creation or update, no problems.  If I have more than 5 an error occurs and the whole stack is rolled back.  </p>
  
  <p>The issue is compounded by streams in the template being added dynamically from config files, so order is not deterministic.</p>
  
  <p>Is there a way to use wait conditions to say only do 5 of these at a time? Even this I think will be an issue because I won't know of streams that are being deleted.</p>
  
  <p>OR is there some way to have CloudFormation back off a creation attempt, wait and try again without ROLLBACK on the whole stack?</p>