AWS CloudFormation：リソースの作成をキャンセルさせ、デバッグする原因は何ですか？

Question

私はどのように私は、これは、関連datomicだとは思わないhttps://github.com/vrivellino/clojure-west-2014-demo/blob/master/config/cfn-template.json

からこのcloudformationテンプレートをデバッグするには考えている、私はそれがCFテンプレートと間違って何かだと思う（それは今2歳から）。

私は指示に従いますが、すべてがスムーズに進みますが、雲の状態を確認すると、イベントで次のようなエラーが発生しますが、なぜ失敗したかについての有用な理由はありません。 CFでより多くの情報を入手するにはどうすればテンプレートに問題があるのか​​を知ることができます。

myapp:28:17 UTC-0700 ROLLBACK_COMPLETE AWS::CloudFormation::Stack myapp-staging 
myapp:28:16 UTC-0700 DELETE_COMPLETE AWS::IAM::Role TransRole 
myapp:28:15 UTC-0700 DELETE_COMPLETE AWS::IAM::User CfnUser 
myapp:28:13 UTC-0700 DELETE_COMPLETE AWS::IAM::Role PeerRole  
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::ElasticLoadBalancing::LoadBalancer ElasticLoadBalancer 
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::EC2::SecurityGroup PeerSecGrp 
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::CloudWatch::Alarm DatomicMemIndexMB 
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::CloudWatch::Alarm DatomicAlarm  
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::EC2::SecurityGroup TransactorSecGrp  
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::CloudWatch::Alarm DatomicSuicide 
myapp:28:12 UTC-0700 DELETE_COMPLETE AWS::CloudWatch::Alarm DatomicStoragePutBackoff  
myapp:28:12 UTC-0700 DELETE_IN_PROGRESS AWS::ElasticLoadBalancing::LoadBalancer ElasticLoadBalancer 
myapp:28:12 UTC-0700 DELETE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicAlarm  
myapp:28:12 UTC-0700 DELETE_IN_PROGRESS AWS::IAM::Role TransRole 
myapp:28:12 UTC-0700 DELETE_IN_PROGRESS AWS::IAM::User CfnUser 
myapp:28:12 UTC-0700 DELETE_IN_PROGRESS AWS::EC2::SecurityGroup PeerSecGrp 
myapp:28:12 UTC-0700 DELETE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicStoragePutBackoff  
myapp:28:11 UTC-0700 DELETE_IN_PROGRESS AWS::IAM::Role PeerRole  
myapp:28:11 UTC-0700 DELETE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicSuicide 
myapp:28:11 UTC-0700 DELETE_IN_PROGRESS AWS::EC2::SecurityGroup TransactorSecGrp  
myapp:28:08 UTC-0700 ROLLBACK_IN_PROGRESS AWS::CloudFormation::Stack myapp-staging The following resource(s) failed to create: [TransactorSecGrp, TransRole, PeerRole, PeerSecGrp, ElasticLoadBalancer, CfnUser, DatomicMemIndexMB]. . Rollback requested by user. 
myapp:28:07 UTC-0700 CREATE_FAILED AWS::EC2::SecurityGroup PeerSecGrp Resource creation cancelled 
myapp:28:06 UTC-0700 CREATE_FAILED AWS::EC2::SecurityGroup TransactorSecGrp Resource creation cancelled 
myapp:27:52 UTC-0700 CREATE_FAILED AWS::ElasticLoadBalancing::LoadBalancer ElasticLoadBalancer Resource creation cancelled 
myapp:27:52 UTC-0700 CREATE_FAILED AWS::IAM::User CfnUser Resource creation cancelled 
myapp:27:52 UTC-0700 CREATE_FAILED AWS::IAM::Role TransRole Resource creation cancelled 
myapp:27:52 UTC-0700 CREATE_FAILED AWS::IAM::Role PeerRole Resource creation cancelled 
myapp:27:51 UTC-0700 CREATE_COMPLETE AWS::CloudWatch::Alarm DatomicStoragePutBackoff  
myapp:27:51 UTC-0700 CREATE_COMPLETE AWS::CloudWatch::Alarm DatomicAlarm  
myapp:27:51 UTC-0700 CREATE_IN_PROGRESS AWS::EC2::SecurityGroup PeerSecGrp 
myapp:27:51 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicStoragePutBackoff Resource creation Initiated 
myapp:27:51 UTC-0700 CREATE_COMPLETE AWS::CloudWatch::Alarm DatomicSuicide 
myapp:27:51 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicAlarm Resource creation Initiated 
myapp:27:51 UTC-0700 CREATE_IN_PROGRESS AWS::IAM::User CfnUser Resource creation Initiated 
myapp:27:51 UTC-0700 CREATE_IN_PROGRESS AWS::ElasticLoadBalancing::LoadBalancer ElasticLoadBalancer 
myapp:27:51 UTC-0700 CREATE_FAILED AWS::CloudWatch::Alarm DatomicMemIndexMB A separate request to update this alarm is in progress. 
myapp:27:51 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicSuicide Resource creation Initiated 
Physical ID:myapp-staging-DatomicSuicide-fasfafsf3 
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicStoragePutBackoff  
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::IAM::User CfnUser 
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicAlarm  
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::EC2::SecurityGroup TransactorSecGrp  
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::IAM::Role PeerRole  
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicSuicide 
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::CloudWatch::Alarm DatomicMemIndexMB 
myapp:27:50 UTC-0700 CREATE_IN_PROGRESS AWS::IAM::Role TransRole 
myapp:27:46 UTC-0700 CREATE_IN_PROGRESS AWS::CloudFormation::Stack myapp-staging User Initiated 

Answer 1

私はDatomicについて何も知らないが、イベント中にエラーがポストログは次のとおりです。

myapp:27:51 UTC-0700 CREATE_FAILED AWS::CloudWatch::Alarm DatomicMemIndexMB A separate request to update this alarm is in progress. 

他のエラーは、最初のエラーが発生した後にトリガされResource creation cancelledと自動ロールバックされていますすべての更新/更新リソースが開始されます。

DatomicMemIndexMBAWS::CloudWatch::AlarmのリソースでA separate request to update this alarm is in progressエラーが発生したことを知る以外に、CloudFormationからの情報はありません。 AWS::CloudWatch::Alarmリソースの実装はAWS独自のものであるため、このエラーの意味を詳細に特定することはできません。しかし、既存のCloudWatchアラームが既にDatomicMemIndexMBというような明白なものがある場合、または2つのCloudFormationスタックを同時に作成/更新しようとしている場合は、おそらくこの特定のエラーの原因です。