Updating Parameter Values for CloudFormation StackSets
Question
You are in charge of maintaining several AWS CloudFormation StackSets in a large organization.
One StackSets was created to configure infrastructure resources such as IAM roles and security groups in several regions for a web application.
Recently, due to certain new features of the application, one parameter value of the CloudFormation StackSets needs to be updated.
However, this update is only required for two regions and the other regions should not be changed for the parameter.
How should you implement this?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - C.
In this case, stack instances in two regions need to have different property values than the specified ones when the StackSets was created.
This can be done by overriding parameter values for existing stack instances.
The detailed explanation can be found in https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stackinstances-override.html.
Option A is incorrect: Because parameters of StackSets can be overridden in selected regions.
Users do not need to remove stacks from StackSets.
Option B is incorrect: Because it is unnecessary to create new StackSets for updating parameters.
Option C is CORRECT: Because you can specify particular regions where parameters need to be modified.
Take below screenshots for an example:
1, Select the StackSet and choose Override StackSet parameters.
2, Specify the accounts and regions.
3, Edit the value to true for EnableLogFileValidation.
Option D is incorrect: Because Edit StackSet Details action modifies the parameter values in all regions for the whole StackSet.
Refer to.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-update.htmlfor details.
In this question, Override StackSet parameters should be used.
The correct answer is C. Choose Override StackSet parameters from the Actions menu. Specify the two regions that you want to modify and then override the StackSet parameters for these regions.
Explanation:
StackSets allow you to manage resources across multiple accounts and regions in a single operation. StackSets use CloudFormation stacks as templates to provision and update resources across accounts and regions. When you create a StackSet, you define a set of parameters that are used to configure the resources in the stack for each region and account where the stack is deployed.
In this scenario, the requirement is to update the parameter value for only two regions and leave the others unchanged. Since CloudFormation StackSets do not allow you to modify parameters for specific regions, you need to use the Override StackSet Parameters feature.
The Override StackSet Parameters feature allows you to change the parameter values for a specific region in a CloudFormation StackSet. Here are the steps to follow:
- Open the AWS CloudFormation console.
- Choose the StackSets option from the left navigation pane.
- Select the StackSet that you want to update.
- Choose the Actions drop-down menu and select Override StackSet Parameters.
- In the Override StackSet Parameters dialog box, specify the two regions that you want to modify.
- Specify the new parameter value for these regions.
- Choose Override to confirm the changes.
Once the parameter value is updated, the CloudFormation StackSet will apply the new parameter value to the CloudFormation stacks in the specified regions. The CloudFormation StackSet will not modify the stacks in other regions.
Option A is incorrect because CloudFormation StackSets do not allow you to modify parameters for specific regions without removing the stacks from the StackSet.
Option B is incorrect because deregistering the two regions from the StackSet and creating a new StackSet with the new parameters is time-consuming and error-prone.
Option D is incorrect because the Edit StackSet Details feature allows you to modify only the StackSet settings, such as the StackSet name, description, and tags. It does not allow you to modify parameters for specific regions.
