2 Answers
- Newest
- Most votes
- Most comments
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::NamedQuery
resource 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.
answered 2 years ago
0
Did you do a
sam package
after you removed the NamedQuery resource?
answered 2 years ago
Yes, I do a
sam package
before the deploy. But I have triedsam deploy
right aftersam build
and that returns the same error.
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
Yes, the
NamedQuery
was 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 deploy
Adding a
WaitConditionHandle
, updating the stack and then removing it seems to have done the trick. Thanks for the suggestion @dylanredm0nd!