amazon web services - How to get CloudFormation to respect Kinesis simultaneous stream creation limits -
i have cloudformation stack contains multiple kinesis streams. if stream count less 5 during creation or update, no problems. if have more 5 error occurs , whole stack rolled back.
the issue compounded streams in template being added dynamically config files, order not deterministic.
is there way use wait conditions 5 of these @ time? think issue because won't know of streams being deleted.
or there way have cloudformation off creation attempt, wait , try again without rollback on whole stack?
waitconditions aren't designed this. more setting servers can ping when they're done.
there no creation strategy streams @ time.
according aws response in thread way build dependson chain. suggest batching had linked list since wouldn't know other stacks to. still not full proof won't have more 5 stacks building @ once.
Comments
Post a Comment