AWS CloudFormation：是什么导致资源创建被取消以及如何调试？

Question

我不知道如何调试这个 cloudformation 模板 https://github.com/vrivellino/clojure-west-2014-demo/blob/master/config/cfn-template.json

我不认为这与数据相关，我认为 cf 模板有问题（因为它现在已有 2 年历史）。

我按照指示进行，一切顺利，但是当我检查 cloudformation 时，它会导致事件中出现以下内容失败，但没有提供任何有关失败原因的有用原因。我如何在 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在引发初始错误并启动所有已更新/正在更新资源的自动回滚后触发的。

除了知道错误是在类型 的资源A separate request to update this alarm is in progress上引发的之外，CloudFormation 没有提供更多信息。该资源的实现是 AWS 专有的，因此您无法更详细地确定此错误的确切含义。但是，如果存在明显的情况，例如已命名的现有 CloudWatch 警报，或者您尝试同时创建/更新两个 CloudFormation 堆栈，则可能是导致此特定错误的原因。DatomicMemIndexMBAWS::CloudWatch::AlarmAWS::CloudWatch::AlarmDatomicMemIndexMB