blocks|key|5275508|text|我们遇到了类似的问题，并发现在更新参数的定义时遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5275509|我们的情况是：|5275510|已使用类型为String+default+Dev的参数StageName创建堆栈。|5275511|然后，我们转到使用参数存储，并使用参数存储路径将参数定义更新为AWS::SSM::+parameter+::Value和default类型。|5275512|当调用更新堆栈时，Cloudformation正在读取现有值'+Dev‘，并将其作为默认值传递给参数，因此它会在路径Dev处查找参数存储值。显然，这并不存在，并导致了错误：|5275513|调用CreateChangeSet操作时出错(ValidationError)：无法从此帐户的参数存储区获取参数Dev。|5275514|对我们来说，最简单的修复方法是删除堆栈并重新创建，但可以看到这对其他人来说是一个问题。如果有人有更好的“升级”方法，那将是很好的发现。|5275515|我们对Lambda使用sam+deploy进行部署，所以不确定这是否适用于其他堆栈的update-stack。|5275516|更新**|5275517|我尝试通过create/update+stack重新创建它，但失败了，所以看起来这个问题仅限于pacakge/deploy升级机制|5275518|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|U|$]]

We had a similar issue and found that we hit this issue when updating the definition of the parameter. 

Our situation was: 

Created stack with parameter StageName with type String default Dev.

We then moved to using the parameter store and updated the parameter definition to be of type AWS::SSM::Parameter::Value and default with the parameter store path. 

When calling the update stack, Cloudformation was reading the existing value 'Dev' and passing this in as the default to the parameter and so it was then looking for the parameter store value at path Dev. Obviously this didn't exist and resulted in the error:

An error occurred (ValidationError) when calling the CreateChangeSet operation: Unable to fetch parameters [Dev] from parameter store for this account.

The easiest fix for us was to delete the stack and recreate but can see this being a problem for others. If anybody has a better 'upgrade' method it would be good to find out.

We were deploying using sam deploy for a Lambda so not sure if this applied to update-stack for other stacks.

UPDATE**

I tried recreating this via create/update stack but failed so it looks like this issue is restricted to the pacakge/deploy upgrade mechanism

blocks|key|5275554|text|当您将参数从一个模板传递到另一个模板时，通常会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5275555|Template+1+has+parameter+reading+from+SSM+store+and+passing+it+to+another+template|code-block|syntax|javascript|5275556|Parameters:
++SNSTopicArnParam:
++++Description:+Arn+of+the+SNS+topic
++++Type:+AWS::SSM::Parameter::Value<String>
++++Default:+/arn/topics/topic1
Resources:
++CallOtherStack:
++++Type:+AWS::CloudFormation::Stack
++++Properties:
++++++TemplateURL:+someurl/template2.yaml
++++++Parameters:
++++++++SNSTopicArn:+!Ref+SNSTopicArnParam|5275557|模板2具有以下参数和资源(将出现Unable+to+fetch+parameters错误)。|5275558|Parameters:
++SNSTopicArnFromCaller:
++++Description:+Arn+of+the+SNS+topic
++++Type:+AWS::SSM::Parameter::Value<String>
++++Default:+/arn/topics/topic1
Resources:
++NewSubscription:
++++Type:+AWS::SNS::Subscription
++++Properties:
++++++Parameters:
++++++++TopicArn:+!Ref+SNSTopicArnFromCaller
++++++++Endpoint:+someValue
++++++++Protocol:+SQS|5275559|这是因为模板one的值为/+arn+/topic/topic1(主题的arn+)，并在调用它时将arn值传递给template2。并且template2将该值的类型作为另一个SSM参数。|5275560|要解决此问题，template2参数类型应仅为实际参数值的类型。在这种情况下，它应该是字符串|offset|length|style|BOLD|5275561|因此，模板2应该按如下所示进行更新以正常工作|5275562|Parameters:
++SNSTopicArnFromCaller:
++++Description:+Arn+of+the+SNS+topic
++++Type:+String
Resources:
++NewSubscription:
++++Type:+AWS::SNS::Subscription
++++Properties:
++++++Parameters:
++++++++TopicArn:+!Ref+SNSTopicArnFromCaller
++++++++Endpoint:+someValue
++++++++Protocol:+SQS|5275563|entityMap^0|0|0|0|0|0|0|17|3|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@$Q|17|R|18|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

This usually happens when you pass the parameters from one template to another.

<pre><code>Template 1 has parameter reading from SSM store and passing it to another template
</code></pre>

<pre><code>Parameters:
 SNSTopicArnParam:
 Description: Arn of the SNS topic
 Type: AWS::SSM::Parameter::Value&lt;String&gt;
 Default: /arn/topics/topic1
Resources:
 CallOtherStack:
 Type: AWS::CloudFormation::Stack
 Properties:
 TemplateURL: someurl/template2.yaml
 Parameters:
 SNSTopicArn: !Ref SNSTopicArnParam
</code></pre>

And Template 2 has the following parameter and resources (will be erroring with the Unable to fetch parameters error.)

<pre><code>Parameters:
 SNSTopicArnFromCaller:
 Description: Arn of the SNS topic
 Type: AWS::SSM::Parameter::Value&lt;String&gt;
 Default: /arn/topics/topic1
Resources:
 NewSubscription:
 Type: AWS::SNS::Subscription
 Properties:
 Parameters:
 TopicArn: !Ref SNSTopicArnFromCaller
 Endpoint: someValue
 Protocol: SQS
</code></pre>

This is because the template one would have the value of /arn/topics/topic1 (the arn of the topic) and pass the arn value to template2 while calling it. And template2 has the type of the value as another SSM parameter.

To resolve this, the template2 parameter type should be just the type of the actual parameter value. In this case, it should be String

so, template 2 should be updated as below to work properly

<pre><code>Parameters:
 SNSTopicArnFromCaller:
 Description: Arn of the SNS topic
 Type: String
Resources:
 NewSubscription:
 Type: AWS::SNS::Subscription
 Properties:
 Parameters:
 TopicArn: !Ref SNSTopicArnFromCaller
 Endpoint: someValue
 Protocol: SQS
</code></pre>

blocks|key|3164631|text|我也有同样的问题。已将现有堆栈集实例参数从字符串更新为参数存储区查找，并且三个帐户之一的堆栈实例更新失败，并出现错误Unable+to+fetch+parameters+['string']+from+parameter+store+for+this+account。不幸的是，由于这些实例在生产帐户中，因此不能选择删除和重新部署。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3164632|我向AWS打开了一个支持案例，他们同意了这篇文章中的诊断。以下是建议，它是有效的。|3164633|3164634|在指定参数列表但不带参数值的同时更新阻塞的堆栈实例。这应该会将参数重置为StackSet默认值。使用以下AWS+CLI命令，我成功地完成了此操作：aws+cloudformation+update-stack-instances+--stack-set-name+stack-set-name+--accounts+"############"+--regions+us-east-1+--parameter-overrides|ordered-list-item|3164635|，|3164636|unordered-list-item|3164637|3164638|​|3164639|3164640|尝试使用所需参数再次更新堆栈实例。|3164641|3164642|在我的例子中，我不需要执行步骤2，因为我想使用参数的默认值。其他人可能需要在第二步中传递所需的参数。|3164643|希望这能有所帮助。|3164644|entityMap^0|1M|23|0|0|0|21|3X|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|16|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1A|8|@]|D|@]|E|$]]|$1|N|3|-4|5|O|7|1B|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1D|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]|$1|T|3|U|5|K|7|1F|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1H|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1I|8|@]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|11|$]]

I had the same issue. Updated an existing stack set instance parameter from a string to a parameter store lookup and the stack instance update failed for one of three accounts with error <code>Unable to fetch parameters ['string'] from parameter store for this account</code>. Unfortunately, due to the fact that these instances were in production accounts, deleting and redeploying was not an option. 

I opened a support case with AWS and they agreed with the diagnosis in this thread. The following was the suggestion, which worked. 

<ol>
<li>Update the stuck stack instance while specifying a parameter list but with no parameter values. This should reset the parameters back to the StackSet defaults. 

<ul>
<li>I did this successfully with the following AWS CLI command:
<code>aws cloudformation update-stack-instances --stack-set-name stack-set-name --accounts "############" --regions us-east-1 --parameter-overrides</code></li>
</ul></li>
<li>Attempt to update the stack instance again with the desired parameters.</li>
</ol>

In my case I did not need to perform step 2 because I wanted to use the default value of the parameters. Others may need to pass desired parameters in this second step.

Hope this helps.

blocks|key|289939|text|更新堆栈似乎不会更新堆栈参数的默认值。如果要更新默认值，则需要重命名参数，然后更新堆栈。一旦成功，您可以立即将该参数重新命名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|289940|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

it seems that updating a stack will not update the default value for the stack parameters. if you want to update the default value, you need to rename the parameter and then update the stack. once that works, you can immediately rename the parameter back.

I get the error: 

<pre><code>$ aws cloudformation deploy --template-file ./packaged-stack.yml --stack-name mystackname --capabilities CAPABILITY_NAMED_IAM`


An error occurred (ValidationError) when calling the CreateChangeSet operation: Unable to fetch parameters [XXX] from parameter store for this account.
</code></pre>

What is wrong here? 

The weird thing is <code>XXX</code> is the value from paramter store, so CloudFormation is actually able to get the value ... but it seems like its trying to read from the paramter whose name is the value it got out ... I think my usage is incorrect? 

<pre><code>AWSTemplateFormatVersion : '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: '...'

Parameters:
 BaseStack:
 Type: AWS::SSM::Parameter::Value&lt;String&gt;
 Default: /some/thing/baseStack
</code></pre>

The value stored in <code>/some/thing/baseStack</code> is <code>XXX</code> in this example

Unable to fetch paramters (Param Value) from parameter store for this account

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我得到了错误：$ aws cloudformation deploy --template-file ./packaged-stack.yml --stack-name mystackname --capabilities CAPABILITY_NAMED_IAM`An error occurred (Validati...

问无法从此帐户的参数存储中获取参数(参数值
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法从此帐户的参数存储中获取参数(参数值EN