/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include The input for CreateStack action.See Also:
AWS
* API Reference
The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline const Aws::String& GetStackName() const{ return m_stackName; } /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline bool StackNameHasBeenSet() const { return m_stackNameHasBeenSet; } /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline void SetStackName(const Aws::String& value) { m_stackNameHasBeenSet = true; m_stackName = value; } /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline void SetStackName(Aws::String&& value) { m_stackNameHasBeenSet = true; m_stackName = std::move(value); } /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline void SetStackName(const char* value) { m_stackNameHasBeenSet = true; m_stackName.assign(value); } /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline CreateStackRequest& WithStackName(const Aws::String& value) { SetStackName(value); return *this;} /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline CreateStackRequest& WithStackName(Aws::String&& value) { SetStackName(std::move(value)); return *this;} /** *The name that's associated with the stack. The name must be unique in the * Region in which you are creating the stack.
A stack name can * contain only alphanumeric characters (case sensitive) and hyphens. It must start * with an alphabetical character and can't be longer than 128 characters.
* */ inline CreateStackRequest& WithStackName(const char* value) { SetStackName(value); return *this;} /** *Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Structure containing the template body with a minimum length of 1 byte and a * maximum length of 51,200 bytes. For more information, go to Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
Location of file containing the template body. The URL must point to a * template (max size: 460,800 bytes) that's located in an Amazon S3 bucket or a * Systems Manager document. For more information, go to the Template * anatomy in the CloudFormation User Guide.
Conditional: You must
* specify either the TemplateBody
or the TemplateURL
* parameter, but not both.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
A list of Parameter
structures that specify input parameters for
* the stack. For more information, see the Parameter
* data type.
Set to true
to disable rollback of the stack if stack creation
* failed. You can specify either DisableRollback
or
* OnFailure
, but not both.
Default: false
Set to true
to disable rollback of the stack if stack creation
* failed. You can specify either DisableRollback
or
* OnFailure
, but not both.
Default: false
Set to true
to disable rollback of the stack if stack creation
* failed. You can specify either DisableRollback
or
* OnFailure
, but not both.
Default: false
Set to true
to disable rollback of the stack if stack creation
* failed. You can specify either DisableRollback
or
* OnFailure
, but not both.
Default: false
The rollback triggers for CloudFormation to monitor during stack creation and * updating operations, and for the specified monitoring period afterwards.
*/ inline const RollbackConfiguration& GetRollbackConfiguration() const{ return m_rollbackConfiguration; } /** *The rollback triggers for CloudFormation to monitor during stack creation and * updating operations, and for the specified monitoring period afterwards.
*/ inline bool RollbackConfigurationHasBeenSet() const { return m_rollbackConfigurationHasBeenSet; } /** *The rollback triggers for CloudFormation to monitor during stack creation and * updating operations, and for the specified monitoring period afterwards.
*/ inline void SetRollbackConfiguration(const RollbackConfiguration& value) { m_rollbackConfigurationHasBeenSet = true; m_rollbackConfiguration = value; } /** *The rollback triggers for CloudFormation to monitor during stack creation and * updating operations, and for the specified monitoring period afterwards.
*/ inline void SetRollbackConfiguration(RollbackConfiguration&& value) { m_rollbackConfigurationHasBeenSet = true; m_rollbackConfiguration = std::move(value); } /** *The rollback triggers for CloudFormation to monitor during stack creation and * updating operations, and for the specified monitoring period afterwards.
*/ inline CreateStackRequest& WithRollbackConfiguration(const RollbackConfiguration& value) { SetRollbackConfiguration(value); return *this;} /** *The rollback triggers for CloudFormation to monitor during stack creation and * updating operations, and for the specified monitoring period afterwards.
*/ inline CreateStackRequest& WithRollbackConfiguration(RollbackConfiguration&& value) { SetRollbackConfiguration(std::move(value)); return *this;} /** *The amount of time that can pass before the stack status becomes
* CREATE_FAILED; if DisableRollback
is not set or is set to
* false
, the stack will be rolled back.
The amount of time that can pass before the stack status becomes
* CREATE_FAILED; if DisableRollback
is not set or is set to
* false
, the stack will be rolled back.
The amount of time that can pass before the stack status becomes
* CREATE_FAILED; if DisableRollback
is not set or is set to
* false
, the stack will be rolled back.
The amount of time that can pass before the stack status becomes
* CREATE_FAILED; if DisableRollback
is not set or is set to
* false
, the stack will be rolled back.
The Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline const Aws::VectorThe Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline bool NotificationARNsHasBeenSet() const { return m_notificationARNsHasBeenSet; } /** *The Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline void SetNotificationARNs(const Aws::VectorThe Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline void SetNotificationARNs(Aws::VectorThe Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline CreateStackRequest& WithNotificationARNs(const Aws::VectorThe Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline CreateStackRequest& WithNotificationARNs(Aws::VectorThe Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline CreateStackRequest& AddNotificationARNs(const Aws::String& value) { m_notificationARNsHasBeenSet = true; m_notificationARNs.push_back(value); return *this; } /** *The Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline CreateStackRequest& AddNotificationARNs(Aws::String&& value) { m_notificationARNsHasBeenSet = true; m_notificationARNs.push_back(std::move(value)); return *this; } /** *The Amazon Simple Notification Service (Amazon SNS) topic ARNs to publish * stack related events. You can find your Amazon SNS topic ARNs using the Amazon * SNS console or your Command Line Interface (CLI).
*/ inline CreateStackRequest& AddNotificationARNs(const char* value) { m_notificationARNsHasBeenSet = true; m_notificationARNs.push_back(value); return *this; } /** *In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
In some cases, you must explicitly acknowledge that your stack template * contains certain capabilities in order for CloudFormation to create the * stack.
CAPABILITY_IAM
and
* CAPABILITY_NAMED_IAM
Some stack templates might include * resources that can affect permissions in your Amazon Web Services account; for * example, by creating new Identity and Access Management (IAM) users. For those * stacks, you must explicitly acknowledge this by specifying one of these * capabilities.
The following IAM resources require you to specify either
* the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
* capability.
If you have IAM resources, you can specify either * capability.
If you have IAM resources with custom names, you
* must specify CAPABILITY_NAMED_IAM
.
If you
* don't specify either of these capabilities, CloudFormation returns an
* InsufficientCapabilities
error.
If your stack * template contains these resources, we recommend that you review all permissions * associated with them and edit their permissions if necessary.
For more information, see Acknowledging * IAM Resources in CloudFormation Templates.
* CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros * perform custom processing on templates; this can include simple actions like * find-and-replace operations, all the way to extensive transformations of entire * templates. Because of this, users typically create a change set from the * processed template, so that they can review the changes resulting from the * macros before actually creating the stack. If your stack template contains one * or more macros, and you choose to create a stack directly from the processed * template, without first reviewing the resulting changes in a change set, you * must acknowledge this capability. This includes the AWS::Include * and AWS::Serverless * transforms, which are macros hosted by CloudFormation.
If you want to * create a stack from a stack template that contains macros and nested * stacks, you must create the stack directly from the template using this * capability.
You should only create stacks directly from a * stack template that contains macros if you know what processing the macro * performs.
Each macro relies on an underlying Lambda service function for * processing stack templates. Be aware that the Lambda function owner can update * the function operation without CloudFormation being notified.
*For more information, see Using * CloudFormation macros to perform custom processing on templates.
The template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline const Aws::VectorThe template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline bool ResourceTypesHasBeenSet() const { return m_resourceTypesHasBeenSet; } /** *The template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline void SetResourceTypes(const Aws::VectorThe template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline void SetResourceTypes(Aws::VectorThe template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline CreateStackRequest& WithResourceTypes(const Aws::VectorThe template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline CreateStackRequest& WithResourceTypes(Aws::VectorThe template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline CreateStackRequest& AddResourceTypes(const Aws::String& value) { m_resourceTypesHasBeenSet = true; m_resourceTypes.push_back(value); return *this; } /** *The template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline CreateStackRequest& AddResourceTypes(Aws::String&& value) { m_resourceTypesHasBeenSet = true; m_resourceTypes.push_back(std::move(value)); return *this; } /** *The template resource types that you have permissions to work with for this
* create stack action, such as AWS::EC2::Instance
,
* AWS::EC2::*
, or Custom::MyCustomInstance
. Use the
* following syntax to describe template resource types: AWS::*
(for
* all Amazon Web Services resources), Custom::*
(for all custom
* resources), Custom::logical_ID
(for a specific custom
* resource), AWS::service_name::*
(for all resources of a
* particular Amazon Web Services service), and
* AWS::service_name::resource_logical_ID
(for a
* specific Amazon Web Services resource).
If the list of resource types * doesn't include a resource that you're creating, the stack creation fails. By * default, CloudFormation grants permissions to all resource types. Identity and * Access Management (IAM) uses this parameter for CloudFormation-specific * condition keys in IAM policies. For more information, see Controlling * Access with Identity and Access Management.
*/ inline CreateStackRequest& AddResourceTypes(const char* value) { m_resourceTypesHasBeenSet = true; m_resourceTypes.push_back(value); return *this; } /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline const Aws::String& GetRoleARN() const{ return m_roleARN; } /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline bool RoleARNHasBeenSet() const { return m_roleARNHasBeenSet; } /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline void SetRoleARN(const Aws::String& value) { m_roleARNHasBeenSet = true; m_roleARN = value; } /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline void SetRoleARN(Aws::String&& value) { m_roleARNHasBeenSet = true; m_roleARN = std::move(value); } /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline void SetRoleARN(const char* value) { m_roleARNHasBeenSet = true; m_roleARN.assign(value); } /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline CreateStackRequest& WithRoleARN(const Aws::String& value) { SetRoleARN(value); return *this;} /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline CreateStackRequest& WithRoleARN(Aws::String&& value) { SetRoleARN(std::move(value)); return *this;} /** *The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) * role that CloudFormation assumes to create the stack. CloudFormation uses the * role's credentials to make calls on your behalf. CloudFormation always uses this * role for all future operations on the stack. Provided that users have permission * to operate on the stack, CloudFormation uses this role even if the users don't * have permission to pass it. Ensure that the role grants least privilege.
*If you don't specify a value, CloudFormation uses the role that was * previously associated with the stack. If no role is available, CloudFormation * uses a temporary session that's generated from your user credentials.
*/ inline CreateStackRequest& WithRoleARN(const char* value) { SetRoleARN(value); return *this;} /** *Determines what action will be taken if stack creation fails. This must be
* one of: DO_NOTHING
, ROLLBACK
, or DELETE
.
* You can specify either OnFailure
or DisableRollback
,
* but not both.
Default: ROLLBACK
Determines what action will be taken if stack creation fails. This must be
* one of: DO_NOTHING
, ROLLBACK
, or DELETE
.
* You can specify either OnFailure
or DisableRollback
,
* but not both.
Default: ROLLBACK
Determines what action will be taken if stack creation fails. This must be
* one of: DO_NOTHING
, ROLLBACK
, or DELETE
.
* You can specify either OnFailure
or DisableRollback
,
* but not both.
Default: ROLLBACK
Determines what action will be taken if stack creation fails. This must be
* one of: DO_NOTHING
, ROLLBACK
, or DELETE
.
* You can specify either OnFailure
or DisableRollback
,
* but not both.
Default: ROLLBACK
Determines what action will be taken if stack creation fails. This must be
* one of: DO_NOTHING
, ROLLBACK
, or DELETE
.
* You can specify either OnFailure
or DisableRollback
,
* but not both.
Default: ROLLBACK
Determines what action will be taken if stack creation fails. This must be
* one of: DO_NOTHING
, ROLLBACK
, or DELETE
.
* You can specify either OnFailure
or DisableRollback
,
* but not both.
Default: ROLLBACK
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Structure containing the stack policy body. For more information, go to
* Prevent Updates to Stack Resources in the CloudFormation User Guide.
* You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Location of a file containing the stack policy. The URL must point to a
* policy (maximum size: 16 KB) located in an S3 bucket in the same Region as the
* stack. You can specify either the StackPolicyBody
or the
* StackPolicyURL
parameter, but not both.
Key-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline const Aws::VectorKey-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline bool TagsHasBeenSet() const { return m_tagsHasBeenSet; } /** *Key-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline void SetTags(const Aws::VectorKey-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline void SetTags(Aws::VectorKey-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline CreateStackRequest& WithTags(const Aws::VectorKey-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline CreateStackRequest& WithTags(Aws::VectorKey-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline CreateStackRequest& AddTags(const Tag& value) { m_tagsHasBeenSet = true; m_tags.push_back(value); return *this; } /** *Key-value pairs to associate with this stack. CloudFormation also propagates * these tags to the resources created in the stack. A maximum number of 50 tags * can be specified.
*/ inline CreateStackRequest& AddTags(Tag&& value) { m_tagsHasBeenSet = true; m_tags.push_back(std::move(value)); return *this; } /** *A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
A unique identifier for this CreateStack
request. Specify this
* token if you plan to retry requests so that CloudFormation knows that you're not
* attempting to create a stack with the same name. You might retry
* CreateStack
requests to ensure that CloudFormation successfully
* received them.
All events initiated by a given stack operation are
* assigned the same client request token, which you can use to track operations.
* For example, if you execute a CreateStack
operation with the token
* token1
, then all the StackEvents
generated by that
* operation will have ClientRequestToken
set as
* token1
.
In the console, stack operations display the client
* request token on the Events tab. Stack operations that are initiated from the
* console use the token format Console-StackOperation-ID, which helps you
* easily identify the stack operation . For example, if you create a stack using
* the console, each stack event would be assigned the same token in the following
* format:
* Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
Whether to enable termination protection on the specified stack. If a user * attempts to delete a stack with termination protection enabled, the operation * fails and the stack remains unchanged. For more information, see Protecting * a Stack From Being Deleted in the CloudFormation User Guide. * Termination protection is deactivated on stacks by default.
For nested * stacks, termination protection is set on the root stack and can't be changed * directly on the nested stack.
*/ inline bool GetEnableTerminationProtection() const{ return m_enableTerminationProtection; } /** *Whether to enable termination protection on the specified stack. If a user * attempts to delete a stack with termination protection enabled, the operation * fails and the stack remains unchanged. For more information, see Protecting * a Stack From Being Deleted in the CloudFormation User Guide. * Termination protection is deactivated on stacks by default.
For nested * stacks, termination protection is set on the root stack and can't be changed * directly on the nested stack.
*/ inline bool EnableTerminationProtectionHasBeenSet() const { return m_enableTerminationProtectionHasBeenSet; } /** *Whether to enable termination protection on the specified stack. If a user * attempts to delete a stack with termination protection enabled, the operation * fails and the stack remains unchanged. For more information, see Protecting * a Stack From Being Deleted in the CloudFormation User Guide. * Termination protection is deactivated on stacks by default.
For nested * stacks, termination protection is set on the root stack and can't be changed * directly on the nested stack.
*/ inline void SetEnableTerminationProtection(bool value) { m_enableTerminationProtectionHasBeenSet = true; m_enableTerminationProtection = value; } /** *Whether to enable termination protection on the specified stack. If a user * attempts to delete a stack with termination protection enabled, the operation * fails and the stack remains unchanged. For more information, see Protecting * a Stack From Being Deleted in the CloudFormation User Guide. * Termination protection is deactivated on stacks by default.
For nested * stacks, termination protection is set on the root stack and can't be changed * directly on the nested stack.
*/ inline CreateStackRequest& WithEnableTerminationProtection(bool value) { SetEnableTerminationProtection(value); return *this;} /** *This deletion policy deletes newly created resources, but retains existing
* resources, when a stack operation is rolled back. This ensures new, empty, and
* unused resources are deleted, while critical resources and their data are
* retained. RetainExceptOnCreate
can be specified for any resource
* that supports the
* DeletionPolicy attribute.
This deletion policy deletes newly created resources, but retains existing
* resources, when a stack operation is rolled back. This ensures new, empty, and
* unused resources are deleted, while critical resources and their data are
* retained. RetainExceptOnCreate
can be specified for any resource
* that supports the
* DeletionPolicy attribute.
This deletion policy deletes newly created resources, but retains existing
* resources, when a stack operation is rolled back. This ensures new, empty, and
* unused resources are deleted, while critical resources and their data are
* retained. RetainExceptOnCreate
can be specified for any resource
* that supports the
* DeletionPolicy attribute.
This deletion policy deletes newly created resources, but retains existing
* resources, when a stack operation is rolled back. This ensures new, empty, and
* unused resources are deleted, while critical resources and their data are
* retained. RetainExceptOnCreate
can be specified for any resource
* that supports the
* DeletionPolicy attribute.