描述嵌套CloudFormation堆栈资源的正确方法是什么？

我们有一个CloudFormation脚本，它有四个嵌套堆栈。我试图描述这些嵌套堆栈的资源。但是，当我的describe-stack-resources具有其中一个嵌套堆栈的物理ID时，它只返回“父”堆栈（资源只是嵌套堆栈）。此行为在JavaScript SDK和AWS CLI中一致。描述嵌套CloudFormation堆栈资源的正确方法是什么？

我正在做这个对吗？这是一个错误？有没有解决方法？

例AWS CLI请求：

（注：所要求的物理资源ID是第二即所返回）

aws cloudformation describe-stack-resources --physical-resource-id arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk-DatabaseStack-W12E3SAXPG6K/b0197770-7519-11e6-9518-50aXXXXXca9a 
{ 
    "StackResources": [ 
     { 
      "StackId": "arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk/f93b5960-7518-11e6-8939-XXXXX0f2ad1e", 
      "ResourceStatus": "UPDATE_COMPLETE", 
      "ResourceType": "AWS::CloudFormation::Stack", 
      "Timestamp": "2016-09-07T16:53:11.305Z", 
      "StackName": "pelorus-vk", 
      "PhysicalResourceId": "arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk-DashboardStack-1GDLBCAFE6U3F/fb9c53d0-7518-11e6-bd48-50dXXXXX84d2", 
      "LogicalResourceId": "DashboardStack" 
     }, 
     { 
      "StackId": "arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk/f93b5960-7518-11e6-8939-XXXXX0f2ad1e", 
      "ResourceStatus": "CREATE_COMPLETE", 
      "ResourceType": "AWS::CloudFormation::Stack", 
      "Timestamp": "2016-09-07T16:53:04.667Z", 
      "StackName": "pelorus-vk", 
      "PhysicalResourceId": "arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk-DatabaseStack-W12E3SAXPG6K/b0197770-7519-11e6-9518-50aXXXXXca9a", 
      "LogicalResourceId": "DatabaseStack" 
     }, 
     { 
      "StackId": "arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk/f93b5960-7518-11e6-8939-XXXXX0f2ad1e", 
      "ResourceStatus": "UPDATE_COMPLETE", 
      "ResourceType": "AWS::CloudFormation::Stack", 
      "Timestamp": "2016-09-07T16:53:13.293Z", 
      "StackName": "pelorus-vk", 
      "PhysicalResourceId": "arn:aws:cloudformation:us-west-2:58701038XXXX:stack/pelorus-vk-EventProcessingStack-GB814FASNNV4/fb8f3470-7518-11e6-a2c5-503XXXXXadae", 
      "LogicalResourceId": "EventProcessingStack" 
     }, 
     { 
      "StackId": "arn:aws:cloudformation:us-west-2:587010381366:stack/pelorus-vk/f93b5960-7518-11e6-8939-XXXXX0f2ad1e", 
      "ResourceStatus": "UPDATE_COMPLETE", 
      "ResourceType": "AWS::CloudFormation::Stack", 
      "Timestamp": "2016-09-07T16:53:11.496Z", 
      "StackName": "pelorus-vk", 
      "PhysicalResourceId": "arn:aws:cloudformation:us-west-2:587010381366:stack/pelorus-vk-StreamStack-NAA3DJMELCFG/04990c30-7519-11e6-934e-50aXXXXX12f2", 
      "LogicalResourceId": "StreamStack" 
     } 
    ] 
}

来源

2016-09-08 Dan Mandle

一个潜在的解决方法：在我所期望的行为更换--physical-resource-id与--stack-name结果，即使我提供了物理ID

来源

2016-09-08 21:28:15

描述嵌套CloudFormation堆栈资源的正确方法是什么？

回答

相关问题