CloudFormation Parameters Not Showing Resolved Values

0

According to the CloudFormation Parameters documentation, SSM parameters are meant to be displayed on the Parameters tab on the CloudFormation stack console: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html#aws-ssm-parameter-types

However, I'm not seeing this. There is the Key values, i.e. BucketName, and the Value value, i.e. {{resolve:ssm:/cloudformation/bucket.yaml/BucketName:1}}, but nothing under Resolved value even though CloudFormation is successfully reading the data from Parameter Store. How do I get the value actually used to be displayed?

asked 4 months ago218 views
2 Answers
0

Hi,

Yes, you should get resolved values: I just took this example on 1 of my stacks:

Enter image description here

If the column "Resolved valus" remains empty for you, you should open a Support case via the console of your AWS account.

Note: I remember having to activate a new version of the CFN interface a few weeks ago. Are you sure to have last version of the CFN UI?

Best,

Didier

profile pictureAWS
EXPERT
answered 4 months ago
0

CloudFormation Parameters: These are variables you define within your CloudFormation template. They allow you to customize your infrastructure during stack creation or updates by providing values at deployment time. This makes templates reusable across different environments.

SSM Parameters: These reside in AWS Systems Manager Parameter Store. They offer a secure way to centrally manage configuration settings for your AWS resources. While SSM parameters aren't directly displayed on the CloudFormation Parameters tab, you can use them within your templates to reference values dynamically. This enhances reusability and reduces the risk of hardcoding sensitive information in templates.

Here are some steps to troubleshoot CloudFormation stack issues:

  • Review Stack Events: The CloudFormation console provides a detailed view of events that occurred during stack creation or updates. This can help pinpoint errors or identify resource-specific problems.
  • Check Stack Status: Stacks can have statuses like CREATE_IN_PROGRESS, CREATE_FAILED, or UPDATE_ROLLBACK_FAILED. Understanding the status can guide you towards potential causes.
  • Examine Stack Outputs: If your stack successfully created outputs, these can reveal valuable information about the deployed resources.
  • AWS CloudTrail Logs: Enable CloudTrail to log CloudFormation API calls. These logs can provide insights into user activity and potential API errors.
  • AWS X-Ray (Optional): For in-depth tracing, consider using X-Ray to visualize service calls made during stack operations. This can help identify bottlenecks or pinpoint issues within AWS services involved in your stack.

for more info check these links

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html

https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html

https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/QuickStartCloudFormation.html

profile picture
EXPERT
Sandeep
answered 4 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions