AWS CloudFormation StackSets deploy action reference (original) (raw)

CodePipeline offers the ability to perform AWS CloudFormation StackSets operations as part of your CI/CD process. You use a stack set to create stacks in AWS accounts across AWS Regions by using a single AWS CloudFormation template. All the resources included in each stack are defined by the stack set’s AWS CloudFormation template. When you create the stack set, you specify the template to use, as well as any parameters and capabilities that the template requires.

For more information about concepts for AWS CloudFormation StackSets, see StackSets concepts in the AWS CloudFormation User Guide.

You integrate your pipeline with AWS CloudFormation StackSets through two distinct action types that you use together:

You can use these actions to deploy to target AWS accounts or target AWS Organizations organizational unit IDs.

Note

To deploy to target AWS Organizations accounts or organizational unit IDs and use the service-managed permissions model, you must enable trusted access between AWS CloudFormation StackSets and AWS Organizations. For more information, see Enabling trusted access with AWS CloudFormation Stacksets.

Topics

How AWS CloudFormation StackSets actions work

A CloudFormationStackSet action creates or updates resources depending on whether the action is running for the first time.

The CloudFormationStackSet action creates or updates the stack set and deploys those changes to specified instances.

Note

If you use this action to make an update that includes adding stack instances, the new instances are deployed first and the update is completed last. The new instances first receive the old version, and then the update is applied to all instances.

The CloudFormationStackInstances action creates new stack instances or updates outdated stack instances. An instance becomes outdated when a stack set is updated, but not all instances within it are updated.

As part of an update, the CloudFormationStackSet andCloudFormationStackInstances actions can specify new deployment targets, which creates new stack instances.

As part of an update, the CloudFormationStackSet andCloudFormationStackInstances actions do not delete stack sets, instances, or resources. When the action updates a stack but does not specify all instances to be updated, the instances that were not specified for update are removed from the update and set to a status of OUTDATED.

During a deployment, stack instances can also show a status of OUTDATED if the deployment to instances failed.

How to structure StackSets actions in a pipeline

As a best practice, you should construct your pipeline so that the stack set is created and initially deploys to a subset or a single instance. After you test your deployment and view the generated stack set, then add theCloudFormationStackInstances action so that the remaining instances are created and updated.

Use the console or the CLI to create the recommended pipeline structure as follows:

  1. Create a pipeline with a source action (required) and theCloudFormationStackSet action as the deploy action. Run your pipeline.
  2. When your pipeline first runs, the CloudFormationStackSet action_creates_ your stack set and at least one initial instance. Verify the stack set creation and review the deployment to your initial instance. For example, for initial stack set creation for account Account-A where us-east-1 is the specified Region, the stack instance is created with the stack set:
    Stack instance Region Status
    StackInstanceID-1 us-east-1 CURRENT
  3. Edit your pipeline to add CloudFormationStackInstances as the second deployment action to create/update stack instances for the targets you designate. For example, for stack instance creation for accountAccount-A where the us-east-2 andeu-central-1 Regions are specified, the remaining stack instances are created and the initial instance remains updated as follows:
    Stack instance Region Status
    StackInstanceID-1 us-east-1 CURRENT
    StackInstanceID-2 us-east-2 CURRENT
    StackInstanceID-3 eu-central-1 CURRENT
  4. Run your pipeline as needed to update your stack set and update or create stack instances.

When you initiate a stack update where you have removed deployment targets from the action configuration, then the stack instances that were not designated for update are removed from the deployment and move into an OUTDATED status. For example, for stack instance update for account Account-A where the us-east-2 Region is removed from the action configuration, the remaining stack instances are created and the removed instance is set to OUTDATED as follows:

Stack instance Region Status
StackInstanceID-1 us-east-1 CURRENT
StackInstanceID-2 us-east-2 OUTDATED
StackInstanceID-3 eu-central-1 CURRENT

For more information about best practices for deploying stack sets, see Best practices for StackSets in the AWS CloudFormation User Guide.

The CloudFormationStackSet action

This action creates or updates a stack set from the template stored in the pipeline source location.

After you define a stack set, you can create, update, or delete stacks in the target accounts and Regions specified in the configuration parameters. When creating, updating and deleting stacks, you can specify other preferences, such as the order of Regions for operations to be performed, the failure tolerance percentage beyond which stack operations stop, and the number of accounts in which operations are performed on stacks concurrently.

A stack set is a regional resource. If you create a stack set in one AWS Region, you cannot access it from other Regions.

When this action is used as an update action to the stack set, updates to the stack are not allowed without a deployment to at least one stack instance.

Topics

Action type

Configuration parameters

StackSetName

Required: Yes

The name to associate with the stack set. This name must be unique in the Region where it is created.

The name may only contain alphanumeric and hyphen characters. It must begin with an alphabetic character and be 128 characters or fewer.

Description

Required: No

A description of the stack set. You can use this to describe the stack set’s purpose or other relevant information.

TemplatePath

Required: Yes

The location of the template that defines the resources in the stack set. This must point to a template with a maximum size of 460,800 bytes.

Enter the path to the source artifact name and template file in the format "InputArtifactName::TemplateFileName", as shown in the following example.

SourceArtifact::template.txt

Parameters

Required: No

A list of template parameters for your stack set that update during a deployment.

You can provide parameters as a literal list or a file path:

ParameterKey=BucketName,ParameterValue=amzn-s3-demo-source-bucket

The following example shows an entry with multiple parameters: 

                                                                                                        
  ParameterKey=BucketName,ParameterValue=amzn-s3-demo-source-bucket  
  ParameterKey=Asset1,ParameterValue=true  
  ParameterKey=Asset2,ParameterValue=true  
SourceArtifact::parameters.txt

The following example shows the file contents forparameters.txt. 

[  
    {  
        "ParameterKey": "KeyName",  
        "ParameterValue": "true"  
    },  
    {  
        "ParameterKey": "KeyName",  
        "ParameterValue": "true"  
    }  
]

Capabilities

Required: No

Indicates that the template can create and update resources, depending on the types of resources in the template.

You must use this property if you have IAM resources in your stack template or you create a stack directly from a template containing macros. For the AWS CloudFormation action to successfully operate in this way, you must use one of the following capabilities:

You can specify more than one capability by using a comma and no spaces between capabilities. The example in Example CloudFormationStackSet action configuration shows an entry with multiple capabilities.

PermissionModel

Required: No

Determines how IAM roles are created and managed. If the field is not specified, the default is used. For information, see Permissions models for stack set operations.

Valid values are:

Note

This parameter can only be changed when no stack instances exist in the stack set.

**AdministrationRoleArn

Note

Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set.

Required: No

Note

This parameter is optional for the SELF_MANAGED permissions model and is not used for the SERVICE_MANAGED permissions model.

The ARN of the IAM role in the administrator account used to perform stack set operations.

The name may contain alphanumeric characters, any of the following characters: _+=,.@-, and no spaces. The name is not case sensitive. This role name must be a minimum length of 20 characters and maximum length of 2048 characters. Role names must be unique within the account. The role name specified here must be an existing role name. If you do not specify the role name, it is set to AWSCloudFormationStackSetAdministrationRole. If you specify ServiceManaged, you must not define a role name.

**ExecutionRoleName

Note

Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set.

Required: No

Note

This parameter is optional for the SELF_MANAGED permissions model and is not used for the SERVICE_MANAGED permissions model.

The name of the IAM role in the target accounts used to perform stack set operations. The name may contain alphanumeric characters, any of the following characters: _+=,.@-, and no spaces. The name is not case sensitive. This role name must be a minimum length of 1 character and maximum length of 64 characters. Role names must be unique within the account. The role name specified here must be an existing role name. Do not specify this role if you are using customized execution roles. If you do not specify the role name, it is set toAWSCloudFormationStackSetExecutionRole. If you set Service_Managed to true, you must not define a role name.

**OrganizationsAutoDeployment

Required: No

Note

This parameter is optional for the SERVICE_MANAGED permissions model and is not used for the SELF_MANAGED permissions model.

Describes whether AWS CloudFormation StackSets automatically deploys to AWS Organizations accounts that are added to a target organization or organizational unit (OU). If OrganizationsAutoDeployment is specified, do not specify DeploymentTargets andRegions.

Note

If no input is provided forOrganizationsAutoDeployment, then the default value is Disabled.

Valid values are:

**DeploymentTargets

Required: No

Note

For the SERVICE_MANAGED permissions model, you can provide either the organization root ID or organizational Unit IDs for deployment targets. For the SELF_MANAGED permissions model, you can only provide accounts.

Note

When this parameter is selected, you must also select Regions.

A list of AWS accounts or organizational unit IDs where stack set instances should be created/updated.

Note

This parameter is optional for the SERVICE_MANAGED permissions model and is not used for the SELF_MANAGED permissions model. Do not use this if you select OrganizationsAutoDeployment.
The AWS organizational units in which to update associated stack instances.
You can provide organizational unit IDs as a literal list or a file path: 

ou-examplerootid111-exampleouid111,ou-examplerootid222-exampleouid222  
SourceArtifact::OU-IDs.txt

The following example shows the file contents forOU-IDs.txt: 

[  
    "ou-examplerootid111-exampleouid111","ou-examplerootid222-exampleouid222"  
]

**Regions

Required: No

Note

When this parameter is selected, you must also select DeploymentTargets.

A list of AWS Regions where stack set instances are created or updated. Regions are updated in the order in which they are entered.

Enter a list of valid AWS Regions in the formatRegion1,Region2, as shown in the following example.

us-west-2,us-east-1

**FailureTolerancePercentage

Required: No

The percentage of accounts per Region for which this stack operation can fail before AWS CloudFormation stops the operation in that Region. If the operation is stopped in a Region, AWS CloudFormation doesn't attempt the operation in subsequent Regions. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds down to the next whole number.

**MaxConcurrentPercentage

Required: No

The maximum percentage of accounts in which to perform this operation at one time. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds down to the next whole number. If rounding down would result in zero, AWS CloudFormation sets the number as one instead. Although you use this setting to specify the maximum, for large deployments the actual number of accounts acted upon concurrently may be lower due to service throttling.

RegionConcurrencyType

Required: No

You can specify if the stack set should deploy across AWS Regions sequentially or in parallel by configuring the Region concurrency deployment parameter. When the Region concurrency is specified to deploy stacks across multiple AWS Regions in parallel, this can result in faster overall deployment times.

ConcurrencyMode

Required: No

The concurrency mode allows you to choose how the concurrency level behaves during stack set operations, whether with strict or soft failure tolerance. Strict Failure Tolerance lowers the deployment speed as stack set operation failures occur because concurrency decreases for each failure. Soft Failure Tolerance prioritizes deployment speed while still leveraging AWS CloudFormation safety capabilities.

CallAs

Required: No

Note

This parameter is optional for the SERVICE_MANAGED permissions model and is not used for the SELF_MANAGED permissions model.

Specifies whether you are acting in the organization's management account or as a delegated administrator in a member account.

Note

If this parameter is set to DELEGATED_ADMIN, make sure that the pipeline IAM role hasorganizations:ListDelegatedAdministrators permission. Otherwise, the action will fail while running with an error similar to the following:Account used is not a delegated administrator.

Input artifacts

You must include at least one input artifact that contains the template for the stack set in a CloudFormationStackSet action. You can include more input artifacts for lists of deployment targets, accounts, and parameters.

Output artifacts

Output variables

If you configure this action, it produces variables that can be referenced by the action configuration of a downstream action in the pipeline. You configure an action with a namespace to make those variables available to the configuration of downstream actions.

For more information, see Variables reference.

Example CloudFormationStackSet action configuration

The following examples show the action configuration for the CloudFormationStackSet action.

Example for the self-managed permissions model

The following example shows a CloudFormationStackSet action where the deployment target entered is an AWS account ID.

YAML

Name: CreateStackSet
ActionTypeId:
  Category: Deploy
  Owner: AWS
  Provider: CloudFormationStackSet
  Version: '1'
RunOrder: 1
Configuration:
  DeploymentTargets: '111111222222'
  FailureTolerancePercentage: '20'
  MaxConcurrentPercentage: '25'
  PermissionModel: SELF_MANAGED
  Regions: us-east-1
  StackSetName: my-stackset
  TemplatePath: 'SourceArtifact::template.json'
OutputArtifacts: []
InputArtifacts:
  - Name: SourceArtifact
Region: us-west-2
Namespace: DeployVariables

JSON

{
    "Name": "CreateStackSet",
    "ActionTypeId": {
        "Category": "Deploy",
        "Owner": "AWS",
        "Provider": "CloudFormationStackSet",
        "Version": "1"
    },
    "RunOrder": 1,
    "Configuration": {
        "DeploymentTargets": "111111222222",
        "FailureTolerancePercentage": "20",
        "MaxConcurrentPercentage": "25",
        "PermissionModel": "SELF_MANAGED",
        "Regions": "us-east-1",
        "StackSetName": "my-stackset",
        "TemplatePath": "SourceArtifact::template.json"
    },
    "OutputArtifacts": [],
    "InputArtifacts": [
        {
            "Name": "SourceArtifact"
        }
    ],
    "Region": "us-west-2",
    "Namespace": "DeployVariables"
}

Example for the service-managed permissions model

The following example shows a CloudFormationStackSet action for the service-managed permissions model where the option for auto deployment to AWS Organizations is enabled with stack retention.

YAML

Name: Deploy
ActionTypeId:
  Category: Deploy
  Owner: AWS
  Provider: CloudFormationStackSet
  Version: '1'
RunOrder: 1
Configuration:
  Capabilities: 'CAPABILITY_IAM,CAPABILITY_NAMED_IAM'
  OrganizationsAutoDeployment: EnabledWithStackRetention
  PermissionModel: SERVICE_MANAGED
  StackSetName: stacks-orgs
  TemplatePath: 'SourceArtifact::template.json'
OutputArtifacts: []
InputArtifacts:
  - Name: SourceArtifact
Region: eu-central-1
Namespace: DeployVariables

JSON

{
    "Name": "Deploy",
    "ActionTypeId": {
        "Category": "Deploy",
        "Owner": "AWS",
        "Provider": "CloudFormationStackSet",
        "Version": "1"
    },
    "RunOrder": 1,
    "Configuration": {
        "Capabilities": "CAPABILITY_IAM,CAPABILITY_NAMED_IAM",
        "OrganizationsAutoDeployment": "EnabledWithStackRetention",
        "PermissionModel": "SERVICE_MANAGED",
        "StackSetName": "stacks-orgs",
        "TemplatePath": "SourceArtifact::template.json"
    },
    "OutputArtifacts": [],
    "InputArtifacts": [
        {
            "Name": "SourceArtifact"
        }
    ],
    "Region": "eu-central-1",
    "Namespace": "DeployVariables"
}

The CloudFormationStackInstances action

This action creates new instances and deploys stack sets to specified instances. A stack instance is a reference to a stack in a target account within a Region. A stack instance can exist without a stack; for example, if the stack creation is not successful, the stack instance shows the reason for stack creation failure. A stack instance is associated with only one stack set.

After the initial creation of a stack set, you can add new stack instances by usingCloudFormationStackInstances. Template parameter values can be overridden at the stack instance level during create or update stack set instance operations.

Each stack set has one template and set of template parameters. When you update the template or template parameters, you update them for the entire set. Then all instance statuses are set to OUTDATED until the changes are deployed to that instance.

To override parameter values on specific instances, for example, if the template contains a parameter for stage with a value of prod, you can override the value of that parameter to be beta orgamma.

Topics

Action type

Configuration parameters

StackSetName

Required: Yes

The name to associate with the stack set. This name must be unique in the Region where it is created.

The name may only contain alphanumeric and hyphen characters. It must begin with an alphabetic character and be 128 characters or fewer.

**DeploymentTargets

Required: No

Note

For the SERVICE_MANAGED permissions model, you can provide either the organization root ID or organizational Unit IDs for deployment targets. For the SELF_MANAGED permissions model, you can only provide accounts.

Note

When this parameter is selected, you must also select Regions.

A list of AWS accounts or organizational unit IDs where stack set instances should be created/updated.

Note

This parameter is optional for the SERVICE_MANAGED permissions model and is not used for the SELF_MANAGED permissions model. Do not use this if you select OrganizationsAutoDeployment.
The AWS organizational units in which to update associated stack instances.
You can provide organizational unit IDs as a literal list or a file path. 

ou-examplerootid111-exampleouid111,ou-examplerootid222-exampleouid222  
SourceArtifact::OU-IDs.txt

The following example shows the file contents forOU-IDs.txt: 

[  
    "ou-examplerootid111-exampleouid111","ou-examplerootid222-exampleouid222"  
]

**Regions

Required: Yes

Note

When this parameter is selected, you must also select DeploymentTargets.

A list of AWS Regions where stack set instances are created or updated. Regions are updated in the order in which they are entered.

Enter a list of valid AWS Regions in the format:Region1,Region2, as shown in the following example.

us-west-2,us-east-1

ParameterOverrides

Required: No

A list of stack set parameters that you want to override in the selected stack instances. Overridden parameter values are applied to all stack instances in the specified accounts and Regions.

You can provide parameters as a literal list or a file path:

ParameterKey=BucketName,ParameterValue=amzn-s3-demo-source-bucket

The following example shows an entry with multiple parameters. 

                                                                                                        
  ParameterKey=BucketName,ParameterValue=amzn-s3-demo-source-bucket  
  ParameterKey=Asset1,ParameterValue=true  
  ParameterKey=Asset2,ParameterValue=true  
SourceArtifact::parameter-overrides.txt

The following example shows the file contents forparameter-overrides.txt. 

[  
    {  
        "ParameterKey": "KeyName",  
        "ParameterValue": "true"  
    },  
    {  
        "ParameterKey": "KeyName",  
        "ParameterValue": "true"  
    }  
]

**FailureTolerancePercentage

Required: No

The percentage of accounts per Region for which this stack operation can fail before AWS CloudFormation stops the operation in that Region. If the operation is stopped in a Region, AWS CloudFormation doesn't attempt the operation in subsequent Regions. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds down to the next whole number.

**MaxConcurrentPercentage

Required: No

The maximum percentage of accounts on which to perform this operation at one time. When calculating the number of accounts based on the specified percentage, AWS CloudFormation rounds down to the next whole number. If rounding down would result in zero, AWS CloudFormation sets the number as one instead. Although you specify the maximum, for large deployments the actual number of accounts acted upon concurrently may be lower due to service throttling.

RegionConcurrencyType

Required: No

You can specify if the stack set should deploy across AWS Regions sequentially or in parallel by configuring the region concurrency deployment parameter. When the Region concurrency is specified to deploy stacks across multiple AWS Regions in parallel, this can result in faster overall deployment times.

ConcurrencyMode

Required: No

The concurrency mode allows you to choose how the concurrency level behaves during stack set operations, whether with strict or soft failure tolerance. Strict Failure Tolerance lowers the deployment speed as stack set operation failures occur because concurrency decreases for each failure. Soft Failure Tolerance prioritizes deployment speed while still leveraging AWS CloudFormation safety capabilities.

CallAs

Required: No

Note

This parameter is optional for the SERVICE_MANAGED permissions model and is not used for the SELF_MANAGED permissions model.

Specifies whether you are acting in the organization's management account or as a delegated administrator in a member account.

Note

If this parameter is set to DELEGATED_ADMIN, make sure that the pipeline IAM role hasorganizations:ListDelegatedAdministrators permission. Otherwise, the action will fail while running with an error similar to the following:Account used is not a delegated administrator.

Input artifacts

CloudFormationStackInstances can contain artifacts that list deployment targets and parameters.

Output artifacts

Output variables

When configured, this action produces variables that can be referenced by the action configuration of a downstream action in the pipeline. You configure an action with a namespace to make those variables available to the configuration of downstream actions.

For more information, see Variables reference.

Example action configuration

The following examples show the action configuration for the CloudFormationStackInstances action.

Example for the self-managed permissions model

The following example shows a CloudFormationStackInstances action where the deployment target entered is an AWS account ID 111111222222.

YAML

Name: my-instances
ActionTypeId:
  Category: Deploy
  Owner: AWS
  Provider: CloudFormationStackInstances
  Version: '1'
RunOrder: 2
Configuration:
  DeploymentTargets: '111111222222'
  Regions: 'us-east-1,us-east-2,us-west-1,us-west-2'
  StackSetName: my-stackset
OutputArtifacts: []
InputArtifacts:
  - Name: SourceArtifact
Region: us-west-2

JSON

{
    "Name": "my-instances",
    "ActionTypeId": {
        "Category": "Deploy",
        "Owner": "AWS",
        "Provider": "CloudFormationStackInstances",
        "Version": "1"
    },
    "RunOrder": 2,
    "Configuration": {
        "DeploymentTargets": "111111222222",
        "Regions": "us-east-1,us-east-2,us-west-1,us-west-2",
        "StackSetName": "my-stackset"
    },
    "OutputArtifacts": [],
    "InputArtifacts": [
        {
            "Name": "SourceArtifact"
        }
    ],
    "Region": "us-west-2"
}

Example for the service-managed permissions model

The following example shows a CloudFormationStackInstances action for the service-managed permissions model where the deployment target is an AWS Organizations organizational unit ID ou-1111-1example.

YAML

Name: Instances
ActionTypeId:
  Category: Deploy
  Owner: AWS
  Provider: CloudFormationStackInstances
  Version: '1'
RunOrder: 2
Configuration:
  DeploymentTargets: ou-1111-1example
  Regions: us-east-1
  StackSetName: my-stackset
OutputArtifacts: []
InputArtifacts:
  - Name: SourceArtifact
Region: eu-central-1

JSON

{
    "Name": "Instances",
    "ActionTypeId": {
        "Category": "Deploy",
        "Owner": "AWS",
        "Provider": "CloudFormationStackInstances",
        "Version": "1"
    },
    "RunOrder": 2,
    "Configuration": {
        "DeploymentTargets": "ou-1111-1example",
        "Regions": "us-east-1",
        "StackSetName": "my-stackset"
    },
    "OutputArtifacts": [],
    "InputArtifacts": [
        {
            "Name": "SourceArtifact"
        }
    ],
    "Region": "eu-central-1"
}

Service role permissions:CloudFormationStackSet action

For AWS CloudFormation StackSets actions, the following minimum permissions are required.

For the CloudFormationStackSet action, add the following to your policy statement:

{
    "Effect": "Allow",
    "Action": [
        "cloudformation:CreateStackSet",
        "cloudformation:UpdateStackSet",
        "cloudformation:CreateStackInstances",
        "cloudformation:DescribeStackSetOperation",
        "cloudformation:DescribeStackSet",
        "cloudformation:ListStackInstances"
    ],
    "Resource": "resource_ARN"
},

Service role permissions:CloudFormationStackInstances action

For the CloudFormationStackInstances action, add the following to your policy statement:

{
    "Effect": "Allow",
    "Action": [
        "cloudformation:CreateStackInstances",
        "cloudformation:DescribeStackSetOperation"
    ],
    "Resource": "resource_ARN"
},

Permissions models for stack set operations

Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set. You can define permissions through self-managed permissions or service-managed permissions.

With self-managed permissions, you create the two IAM roles required by StackSets - an administrator role such as the AWSCloudFormationStackSetAdministrationRole in the account where you define the stack set and an execution role such as the AWSCloudFormationStackSetExecutionRole in each of the accounts where you deploy stack set instances. Using this permissions model, StackSets can deploy to any AWS account in which the user has permissions to create an IAM role. For more information, seeGrant self-managed permissions in the AWS CloudFormation User Guide.

Note

Because AWS CloudFormation StackSets performs operations across multiple accounts, you must define the necessary permissions in those accounts before you can create the stack set.

With service-managed permissions, you can deploy stack instances to accounts managed by AWS Organizations. Using this permissions model, you don't have to create the necessary IAM roles because StackSets creates the IAM roles on your behalf. With this model, you can also enable automatic deployments to accounts that are added to the organization in the future. See Enable trusted access with AWS Organizations in the_AWS CloudFormation User Guide_.

Template parameter data types

The template parameters used in stack set operations include the following data types. For more information, see DescribeStackSet.

ParameterKey

"ParameterKey=BucketName,ParameterValue=amzn-s3-demo-source-bucket"

ParameterValue

"ParameterKey=BucketName,ParameterValue=amzn-s3-demo-source-bucket"

UsePreviousValue

"ParameterKey=Asset1,UsePreviousValue=true"

Each stack set has one template and set of template parameters. When you update the template or template parameters, you update them for the entire set. Then all instance statuses are set to OUTDATED until the changes are deployed to that instance.

To override parameter values on specific instances, for example, if the template contains a parameter for stage with a value of prod, you can override the value of that parameter to be beta orgamma.

See also

The following related resources can help you as you work with this action.