2回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
As you mentioned you're deploying the Stack in us-east-1, this would rule out the AWS::Athena::NamedQuery resource not being supported.
Seems to be on the GetTemplateSummary API which is called as part of aws cloudformation deploy and also sam deploy.
- Was the
AWS::Athena::NamedQueryresource previously in the template as part of a condition that did not actually create the resource?
If so, did a subsequent update to the stack fail causing it to rollback?
Performing an update operation directly on the Stack via CloudFormation, for example, adding a WaitConditionHandle and removing it in a subsequent update should allow you to proceed.
回答済み 2年前
0
Did you do a
sam package
after you removed the NamedQuery resource?
回答済み 2年前
Yes, I do a
sam packagebefore the deploy. But I have triedsam deployright aftersam buildand that returns the same error.
関連するコンテンツ
AWS公式更新しました 9ヶ月前- AWS公式更新しました 3年前
Yes, the
NamedQuerywas a conditional resource previously.Interesting, a successful update of your Stack manually (by adding any resource) should bring the template into a consistent state that will pass the GetTemplateSummary and subsequently your
sam deployAdding a
WaitConditionHandle, updating the stack and then removing it seems to have done the trick. Thanks for the suggestion @dylanredm0nd!