stacks
Creates, updates, deletes, gets or lists a stacks resource.
Overview
| Name | stacks |
| Type | Resource |
| Id | aws.cloudformation.stacks |
Fields
The following fields are returned by SELECT queries:
- describe_stacks
- list_stacks
| Name | Datatype | Description |
|---|---|---|
capabilities | string | The capabilities allowed in the stack. |
change_set_id | string | The unique ID of the change set. |
creation_time | string | The time at which the stack was created. |
deletion_mode | string | Specifies the deletion mode for the stack. Possible values are: STANDARD - Use the standard behavior. Specifying this value is the same as not specifying this parameter. FORCE_DELETE_STACK - Delete the stack if it's stuck in a DELETE_FAILED state due to resource deletion failure. |
deletion_time | string | The time the stack was deleted. |
deployment_config | string | The deployment configuration for the stack, including the deployment mode used for stack operations. |
description | string | A user-defined description associated with the stack. |
detailed_status | string | The detailed status of the resource or stack. If CONFIGURATION_COMPLETE is present, the resource or resource configuration phase has completed and the stabilization of the resources is in progress. The StackSets CONFIGURATION_COMPLETE when all of the resources in the stack have reached that event. For more information, see Understand CloudFormation stack creation events in the CloudFormation User Guide. |
disable_rollback | boolean | Boolean to enable or disable rollback on stack creation failures: true: disable rollback. false: enable rollback. |
drift_information | string | Information about whether a stack's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. For more information, see Detect unmanaged configuration changes to stacks and resources with drift detection. |
enable_termination_protection | boolean | Whether termination protection is enabled for the stack. For nested stacks, termination protection is set on the root stack and can't be changed directly on the nested stack. For more information, see Protect a CloudFormation stack from being deleted in the CloudFormation User Guide. |
last_operations | string | Information about the most recent operations performed on this stack. |
last_updated_time | string | The time the stack was last updated. This field will only be returned if the stack has been updated at least once. |
notification_arns | string | Amazon SNS topic Amazon Resource Names (ARNs) to which stack related events are published. |
outputs | string | A list of output structures. |
parameters | string | A list of Parameter structures. |
parent_id | string | For nested stacks, the stack ID of the direct parent of this stack. For the first level of nested stacks, the root stack is also the parent stack. For more information, see Nested stacks in the CloudFormation User Guide. |
retain_except_on_create | boolean | When set to true, newly created resources are deleted when the operation rolls back. This includes newly created resources marked with a deletion policy of Retain. Default: false |
role_arn | string | The Amazon Resource Name (ARN) of an IAM role that's associated with the stack. During a stack operation, CloudFormation uses this role's credentials to make calls on your behalf. |
rollback_configuration | string | The rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards. |
root_id | string | For nested stacks, the stack ID of the top-level stack to which the nested stack ultimately belongs. For more information, see Nested stacks in the CloudFormation User Guide. |
stack_id | string | Unique identifier of the stack. |
stack_name | string | The name associated with the stack. |
stack_status | string | Current status of the stack. |
stack_status_reason | string | Success/failure message associated with the stack status. |
tags | string | A list of Tags that specify information about the stack. |
timeout_in_minutes | integer | The amount of time within which stack creation should complete. |
| Name | Datatype | Description |
|---|---|---|
creation_time | string | The time the stack was created. |
deletion_time | string | The time the stack was deleted. |
drift_information | string | Summarizes information about whether a stack's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. For more information, see Detect unmanaged configuration changes to stacks and resources with drift detection. |
last_operations | string | Information about the most recent operations performed on this stack. |
last_updated_time | string | The time the stack was last updated. This field will only be returned if the stack has been updated at least once. |
parent_id | string | For nested stacks, the stack ID of the direct parent of this stack. For the first level of nested stacks, the root stack is also the parent stack. For more information, see Nested stacks in the CloudFormation User Guide. |
root_id | string | For nested stacks, the stack ID of the top-level stack to which the nested stack ultimately belongs. For more information, see Nested stacks in the CloudFormation User Guide. |
stack_id | string | Unique stack identifier. |
stack_name | string | The name associated with the stack. |
stack_status | string | The current status of the stack. |
stack_status_reason | string | Success/Failure message associated with the stack status. |
template_description | string | The template description of the template used to create the stack. |
Methods
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
describe_stacks | select | StackName, region | NextToken | Returns the description for the specified stack; if no stack name was specified, then it returns the description for all the stacks created. For more information about a stack's event history, see Understand CloudFormation stack creation events in the CloudFormation User Guide. If the stack doesn't exist, a ValidationError is returned. |
list_stacks | select | region | NextToken, StackStatusFilter | Returns the summary information for stacks whose status matches the specified StackStatusFilter. Summary information for stacks that have been deleted is kept for 90 days after the stack is deleted. If no StackStatusFilter is specified, summary information for all stacks is returned (including existing stacks and stacks that have been deleted). |
create_stack | insert | StackName, region | TemplateBody, TemplateURL, Parameters, DisableRollback, RollbackConfiguration, TimeoutInMinutes, NotificationARNs, Capabilities, ResourceTypes, RoleARN, OnFailure, StackPolicyBody, StackPolicyURL, Tags, ClientRequestToken, EnableTerminationProtection, RetainExceptOnCreate, DeploymentConfig, DisableValidation | Creates a stack as specified in the template. After the call completes successfully, the stack creation starts. You can check the status of the stack through the DescribeStacks operation. For more information about creating a stack and monitoring stack progress, see Managing Amazon Web Services resources as a single unit with CloudFormation stacks in the CloudFormation User Guide. |
update_termination_protection | update | EnableTerminationProtection, StackName, region | Updates termination protection for 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 Protect a CloudFormation stack from being deleted in the CloudFormation User Guide. For nested stacks, termination protection is set on the root stack and can't be changed directly on the nested stack. | |
update_stack | update | StackName, region | TemplateBody, TemplateURL, UsePreviousTemplate, StackPolicyDuringUpdateBody, StackPolicyDuringUpdateURL, Parameters, Capabilities, ResourceTypes, RoleARN, RollbackConfiguration, StackPolicyBody, StackPolicyURL, NotificationARNs, Tags, DisableRollback, ClientRequestToken, RetainExceptOnCreate, DeploymentConfig, DisableValidation | Updates a stack as specified in the template. After the call completes successfully, the stack update starts. You can check the status of the stack through the DescribeStacks action. To get a copy of the template for an existing stack, you can use the GetTemplate action. For more information about updating a stack and monitoring the progress of the update, see Managing Amazon Web Services resources as a single unit with CloudFormation stacks in the CloudFormation User Guide. |
delete_stack | delete | StackName, region | RetainResources, RoleARN, ClientRequestToken, DeletionMode, DeploymentConfig | Deletes a specified stack. Once the call completes successfully, stack deletion starts. Deleted stacks don't show up in the DescribeStacks operation if the deletion has been completed successfully. For more information about deleting a stack, see Delete a stack from the CloudFormation console in the CloudFormation User Guide. |
cancel_update_stack | exec | StackName, region | ClientRequestToken | Cancels an update on the specified stack. If the call completes successfully, the stack rolls back the update and reverts to the previous stack configuration. You can cancel only stacks that are in the UPDATE_IN_PROGRESS state. |
continue_update_rollback | exec | StackName, region | RoleARN, ResourcesToSkip, ClientRequestToken | Continues rolling back a stack from UPDATE_ROLLBACK_FAILED to UPDATE_ROLLBACK_COMPLETE state. Depending on the cause of the failure, you can manually fix the error and continue the rollback. By continuing the rollback, you can return your stack to a working state (the UPDATE_ROLLBACK_COMPLETE state) and then try to update the stack again. A stack enters the UPDATE_ROLLBACK_FAILED state when CloudFormation can't roll back all changes after a failed stack update. For example, this might occur when a stack attempts to roll back to an old database that was deleted outside of CloudFormation. Because CloudFormation doesn't know the instance was deleted, it assumes the instance still exists and attempts to roll back to it, causing the update rollback to fail. For more information, see Continue rolling back an update in the CloudFormation User Guide. For information for troubleshooting a failed update rollback, see Update rollback failed. |
detect_stack_drift | exec | StackName, region | LogicalResourceIds | Detects whether a stack's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. For each resource in the stack that supports drift detection, CloudFormation compares the actual configuration of the resource with its expected template configuration. Only resource properties explicitly defined in the stack template are checked for drift. A stack is considered to have drifted if one or more of its resources differ from their expected template configurations. For more information, see Detect unmanaged configuration changes to stacks and resources with drift detection. Use DetectStackDrift to detect drift on all supported resources for a given stack, or DetectStackResourceDrift to detect drift on individual resources. For a list of stack resources that currently support drift detection, see Resource type support for imports and drift detection. DetectStackDrift can take up to several minutes, depending on the number of resources contained within the stack. Use DescribeStackDriftDetectionStatus to monitor the progress of a detect stack drift operation. Once the drift detection operation has completed, use DescribeStackResourceDrifts to return drift information about the stack and its resources. When detecting drift on a stack, CloudFormation doesn't detect drift on any nested stacks belonging to that stack. Perform DetectStackDrift directly on the nested stack itself. |
detect_stack_resource_drift | exec | StackName, LogicalResourceId, region | Returns information about whether a resource's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. This information includes actual and expected property values for resources in which CloudFormation detects drift. Only resource properties explicitly defined in the stack template are checked for drift. For more information about stack and resource drift, see Detect unmanaged configuration changes to stacks and resources with drift detection. Use DetectStackResourceDrift to detect drift on individual resources, or DetectStackDrift to detect drift on all resources in a given stack that support drift detection. Resources that don't currently support drift detection can't be checked. For a list of resources that support drift detection, see Resource type support for imports and drift detection. | |
import_stacks_to_stack_set | exec | StackSetName, region | StackIds, StackIdsUrl, OrganizationalUnitIds, OperationPreferences, OperationId, CallAs | Import existing stacks into a new StackSets. Use the stack import operation to import up to 10 stacks into a new StackSet in the same account as the source stack or in a different administrator account and Region, by specifying the stack ID of the stack you intend to import. |
rollback_stack | exec | StackName, region | RoleARN, ClientRequestToken, RetainExceptOnCreate, DeploymentConfig | When specifying RollbackStack, you preserve the state of previously provisioned resources when an operation fails. You can check the status of the stack through the DescribeStacks operation. Rolls back the specified stack to the last known stable state from CREATE_FAILED or UPDATE_FAILED stack statuses. This operation will delete a stack if it doesn't contain a last known stable state. A last known stable state includes any status in a *_COMPLETE. This includes the following stack statuses. CREATE_COMPLETE UPDATE_COMPLETE UPDATE_ROLLBACK_COMPLETE IMPORT_COMPLETE IMPORT_ROLLBACK_COMPLETE |
signal_resource | exec | StackName, LogicalResourceId, UniqueId, region | Status | Sends a signal to the specified resource with a success or failure status. You can use the SignalResource operation in conjunction with a creation policy or update policy. CloudFormation doesn't proceed with a stack creation or update until resources receive the required number of signals or the timeout period is exceeded. The SignalResource operation is useful in cases where you want to send signals from anywhere other than an Amazon EC2 instance. |
Parameters
Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
| Name | Datatype | Description |
|---|---|---|
EnableTerminationProtection | boolean | Whether to enable termination protection on the specified stack. |
LogicalResourceId | string | The logical ID of the resource that you want to signal. The logical ID is the name of the resource that given in the template. |
StackName | string | The stack name or unique stack ID that includes the resource that you want to signal. |
StackSetName | string | The name of the StackSet. The name must be unique in the Region where you create your StackSet. |
UniqueId | string | A unique ID of the signal. When you signal Amazon EC2 instances or Auto Scaling groups, specify the instance ID that you are signaling as the unique ID. If you send multiple signals to a single resource (such as signaling a wait condition), each signal requires a different unique ID. |
region | string | AWS region (default: us-east-1) |
CallAs | string | By default, SELF is specified. Use SELF for StackSets with self-managed permissions. If you are signed in to the management account, specify SELF. For service managed StackSets, specify DELEGATED_ADMIN. |
Capabilities | array | In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to update 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 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 suggest that you review all permissions associated with them and edit their permissions if necessary. AWS::IAM::AccessKey AWS::IAM::Group AWS::IAM::InstanceProfile AWS::IAM::ManagedPolicy AWS::IAM::Policy AWS::IAM::Role AWS::IAM::User AWS::IAM::UserToGroupAddition 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 updating the stack. If your stack template contains one or more macros, and you choose to update 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 update a stack from a stack template that contains macros and nested stacks, you must update the stack directly from the template using this capability. You should only update 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 Perform custom processing on CloudFormation templates with template macros. Only one of the Capabilities and ResourceType parameters can be specified. |
ClientRequestToken | string | A unique identifier for this RollbackStack request. |
DeletionMode | string | Specifies the deletion mode for the stack. Possible values are: STANDARD - Use the standard behavior. Specifying this value is the same as not specifying this parameter. FORCE_DELETE_STACK - Delete the stack if it's stuck in a DELETE_FAILED state due to resource deletion failure. |
DeploymentConfig | object | The deployment configuration for this stack operation, including the deployment mode. |
DisableRollback | boolean | Preserve the state of previously provisioned resources when an operation fails. Default: False |
DisableValidation | boolean | Set to true to disable pre-deployment validations in changeset or stack operations. Default: false |
EnableTerminationProtection | boolean | 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 Protect CloudFormation stacks 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. |
LogicalResourceIds | array | The logical names of any resources you want to use as filters. |
NextToken | string | The token for the next set of items to return. (You received this token from a previous call.) |
NotificationARNs | array | Amazon Simple Notification Service topic Amazon Resource Names (ARNs) that CloudFormation associates with the stack. Specify an empty list to remove all notification topics. |
OnFailure | string | 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. Although the default setting is ROLLBACK, there is one exception. This exception occurs when a StackSet attempts to deploy a stack instance and the stack instance fails to create successfully. In this case, the CreateStack call overrides the default setting and sets the value of OnFailure to DELETE. Default: ROLLBACK |
OperationId | string | A unique, user defined, identifier for the StackSet operation. |
OperationPreferences | object | The user-specified preferences for how CloudFormation performs a StackSet operation. For more information about maximum concurrent accounts and failure tolerance, see StackSet operation options. |
OrganizationalUnitIds | array | The list of OU ID's to which the imported stacks must be mapped as deployment targets. |
Parameters | array | A list of Parameter structures that specify input parameters for the stack. For more information, see the Parameter data type. |
ResourceTypes | array | Specifies which resource types you can work with, such as AWS::EC2::Instance or Custom::MyCustomInstance. If the list of resource types doesn't include a resource that you're updating, the stack update fails. By default, CloudFormation grants permissions to all resource types. IAM uses this parameter for CloudFormation-specific condition keys in IAM policies. For more information, see Control CloudFormation access with Identity and Access Management. Only one of the Capabilities and ResourceType parameters can be specified. |
ResourcesToSkip | array | A list of the logical IDs of the resources that CloudFormation skips during the continue update rollback operation. You can specify only resources that are in the UPDATE_FAILED state because a rollback failed. You can't specify resources that are in the UPDATE_FAILED state for other reasons, for example, because an update was canceled. To check why a resource update failed, use the DescribeStackResources action, and view the resource status reason. Specify this property to skip rolling back resources that CloudFormation can't successfully roll back. We recommend that you troubleshoot resources before skipping them. CloudFormation sets the status of the specified resources to UPDATE_COMPLETE and continues to roll back the stack. After the rollback is complete, the state of the skipped resources will be inconsistent with the state of the resources in the stack template. Before performing another stack update, you must update the stack or resources to be consistent with each other. If you don't, subsequent stack updates might fail, and the stack will become unrecoverable. Specify the minimum number of resources required to successfully roll back your stack. For example, a failed resource update might cause dependent resources to fail. In this case, it might not be necessary to skip the dependent resources. To skip resources that are part of nested stacks, use the following format: NestedStackName.ResourceLogicalID. If you want to specify the logical ID of a stack resource (Type: AWS::CloudFormation::Stack) in the ResourcesToSkip list, then its corresponding embedded stack must be in one of the following states: DELETE_IN_PROGRESS, DELETE_COMPLETE, or DELETE_FAILED. Don't confuse a child stack's name with its corresponding logical ID defined in the parent stack. For an example of a continue update rollback operation with nested stacks, see Continue rolling back from failed nested stack updates. |
RetainExceptOnCreate | boolean | When set to true, newly created resources are deleted when the operation rolls back. This includes newly created resources marked with a deletion policy of Retain. Default: false |
RetainResources | array | For stacks in the DELETE_FAILED state, a list of resource logical IDs that are associated with the resources you want to retain. During deletion, CloudFormation deletes the stack but doesn't delete the retained resources. Retaining resources is useful when you can't delete a resource, such as a non-empty S3 bucket, but you want to delete the stack. |
RoleARN | string | The Amazon Resource Name (ARN) of an IAM role that CloudFormation assumes to rollback the stack. |
RollbackConfiguration | object | The rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards. |
StackIds | array | The IDs of the stacks you are importing into a StackSet. You import up to 10 stacks per StackSet at a time. Specify either StackIds or StackIdsUrl. |
StackIdsUrl | string | The Amazon S3 URL which contains list of stack ids to be inputted. Specify either StackIds or StackIdsUrl. |
StackPolicyBody | string | Structure that contains a new stack policy body. You can specify either the StackPolicyBody or the StackPolicyURL parameter, but not both. You might update the stack policy, for example, in order to protect a new resource that you created during a stack update. If you don't specify a stack policy, the current policy that is associated with the stack is unchanged. |
StackPolicyDuringUpdateBody | string | Structure that contains the temporary overriding stack policy body. You can specify either the StackPolicyDuringUpdateBody or the StackPolicyDuringUpdateURL parameter, but not both. If you want to update protected resources, specify a temporary overriding stack policy during this update. If you don't specify a stack policy, the current policy that is associated with the stack will be used. |
StackPolicyDuringUpdateURL | string | Location of a file that contains the temporary overriding stack policy. The URL must point to a policy (max size: 16KB) located in an S3 bucket in the same Region as the stack. The location for an Amazon S3 bucket must start with https://. URLs from S3 static websites are not supported. You can specify either the StackPolicyDuringUpdateBody or the StackPolicyDuringUpdateURL parameter, but not both. If you want to update protected resources, specify a temporary overriding stack policy during this update. If you don't specify a stack policy, the current policy that is associated with the stack will be used. |
StackPolicyURL | string | Location of a file that contains the updated stack policy. The URL must point to a policy (max size: 16KB) located in an S3 bucket in the same Region as the stack. The location for an Amazon S3 bucket must start with https://. URLs from S3 static websites are not supported. You can specify either the StackPolicyBody or the StackPolicyURL parameter, but not both. You might update the stack policy, for example, in order to protect a new resource that you created during a stack update. If you don't specify a stack policy, the current policy that is associated with the stack is unchanged. |
StackStatusFilter | array | Stack status to use as a filter. Specify one or more stack status codes to list only stacks with the specified status codes. For a complete list of stack status codes, see the StackStatus parameter of the Stack data type. |
Status | string | The status of the signal, which is either success or failure. A failure signal causes CloudFormation to immediately fail the stack creation or update. |
Tags | array | Key-value pairs to associate with this stack. CloudFormation also propagates these tags to supported resources in the stack. You can specify a maximum number of 50 tags. If you don't specify this parameter, CloudFormation doesn't modify the stack's tags. If you specify an empty value, CloudFormation removes all associated tags. |
TemplateBody | string | Structure that contains the template body with a minimum length of 1 byte and a maximum length of 51,200 bytes. Conditional: You must specify only one of the following parameters: TemplateBody, TemplateURL, or set the UsePreviousTemplate to true. |
TemplateURL | string | The URL of a file that contains the template body. The URL must point to a template that's located in an Amazon S3 bucket or a Systems Manager document. The location for an Amazon S3 bucket must start with https://. Conditional: You must specify only one of the following parameters: TemplateBody, TemplateURL, or set the UsePreviousTemplate to true. |
TimeoutInMinutes | integer | 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. |
UsePreviousTemplate | boolean | Reuse the existing template that is associated with the stack that you are updating. When using templates with the AWS::LanguageExtensions transform, provide the template instead of using UsePreviousTemplate to ensure new parameter values and Systems Manager parameter updates are applied correctly. For more information, see AWS::LanguageExtensions transform. Conditional: You must specify only one of the following parameters: TemplateBody, TemplateURL, or set the UsePreviousTemplate to true. |
SELECT examples
- describe_stacks
- list_stacks
Returns the description for the specified stack; if no stack name was specified, then it returns the description for all the stacks created. For more information about a stack's event history, see Understand CloudFormation stack creation events in the CloudFormation User Guide. If the stack doesn't exist, a ValidationError is returned.
SELECT
capabilities,
change_set_id,
creation_time,
deletion_mode,
deletion_time,
deployment_config,
description,
detailed_status,
disable_rollback,
drift_information,
enable_termination_protection,
last_operations,
last_updated_time,
notification_arns,
outputs,
parameters,
parent_id,
retain_except_on_create,
role_arn,
rollback_configuration,
root_id,
stack_id,
stack_name,
stack_status,
stack_status_reason,
tags,
timeout_in_minutes
FROM aws.cloudformation.stacks
WHERE StackName = '{{ StackName }}' -- required
AND region = '{{ region }}' -- required
AND NextToken = '{{ NextToken }}'
;
Returns the summary information for stacks whose status matches the specified StackStatusFilter. Summary information for stacks that have been deleted is kept for 90 days after the stack is deleted. If no StackStatusFilter is specified, summary information for all stacks is returned (including existing stacks and stacks that have been deleted).
SELECT
creation_time,
deletion_time,
drift_information,
last_operations,
last_updated_time,
parent_id,
root_id,
stack_id,
stack_name,
stack_status,
stack_status_reason,
template_description
FROM aws.cloudformation.stacks
WHERE region = '{{ region }}' -- required
AND NextToken = '{{ NextToken }}'
AND StackStatusFilter = '{{ StackStatusFilter }}'
;
INSERT examples
- create_stack
- Manifest
Creates a stack as specified in the template. After the call completes successfully, the stack creation starts. You can check the status of the stack through the DescribeStacks operation. For more information about creating a stack and monitoring stack progress, see Managing Amazon Web Services resources as a single unit with CloudFormation stacks in the CloudFormation User Guide.
INSERT INTO aws.cloudformation.stacks (
StackName,
region,
TemplateBody,
TemplateURL,
Parameters,
DisableRollback,
RollbackConfiguration,
TimeoutInMinutes,
NotificationARNs,
Capabilities,
ResourceTypes,
RoleARN,
OnFailure,
StackPolicyBody,
StackPolicyURL,
Tags,
ClientRequestToken,
EnableTerminationProtection,
RetainExceptOnCreate,
DeploymentConfig,
DisableValidation
)
SELECT
'{{ StackName }}',
'{{ region }}',
'{{ TemplateBody }}',
'{{ TemplateURL }}',
'{{ Parameters }}',
'{{ DisableRollback }}',
'{{ RollbackConfiguration }}',
'{{ TimeoutInMinutes }}',
'{{ NotificationARNs }}',
'{{ Capabilities }}',
'{{ ResourceTypes }}',
'{{ RoleARN }}',
'{{ OnFailure }}',
'{{ StackPolicyBody }}',
'{{ StackPolicyURL }}',
'{{ Tags }}',
'{{ ClientRequestToken }}',
'{{ EnableTerminationProtection }}',
'{{ RetainExceptOnCreate }}',
'{{ DeploymentConfig }}',
'{{ DisableValidation }}'
RETURNING
line_items
;
# Description fields are for documentation purposes
- name: stacks
props:
- name: StackName
value: "{{ StackName }}"
description: Required parameter for the stacks resource.
- name: region
value: "{{ region }}"
description: Required parameter for the stacks resource.
- name: TemplateBody
value: "{{ TemplateBody }}"
description: Structure that contains the template body with a minimum length of 1 byte and a maximum length of 51,200 bytes. Conditional: You must specify either TemplateBody or TemplateURL, but not both.
description: Structure that contains the template body with a minimum length of 1 byte and a maximum length of 51,200 bytes. Conditional: You must specify either TemplateBody or TemplateURL, but not both.
- name: TemplateURL
value: "{{ TemplateURL }}"
description: The URL of a file that contains the template body. The URL must point to a template (max size: 1 MB) that's located in an Amazon S3 bucket or a Systems Manager document. The location for an Amazon S3 bucket must start with https://. URLs from S3 static websites are not supported. Conditional: You must specify either the TemplateBody or the TemplateURL parameter, but not both.
description: The URL of a file that contains the template body. The URL must point to a template (max size: 1 MB) that's located in an Amazon S3 bucket or a Systems Manager document. The location for an Amazon S3 bucket must start with https://. URLs from S3 static websites are not supported. Conditional: You must specify either the TemplateBody or the TemplateURL parameter, but not both.
- name: Parameters
value: "{{ Parameters }}"
description: A list of Parameter structures that specify input parameters for the stack. For more information, see the Parameter data type.
description: A list of Parameter structures that specify input parameters for the stack. For more information, see the Parameter data type.
- name: DisableRollback
value: {{ DisableRollback }}
description: 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
description: 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
- name: RollbackConfiguration
value: "{{ RollbackConfiguration }}"
description: The rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards.
description: The rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards.
- name: TimeoutInMinutes
value: {{ TimeoutInMinutes }}
description: 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.
description: 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.
- name: NotificationARNs
value: "{{ NotificationARNs }}"
description: The 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).
description: The 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).
- name: Capabilities
value: "{{ Capabilities }}"
description: 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 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. AWS::IAM::AccessKey AWS::IAM::Group AWS::IAM::InstanceProfile AWS::IAM::ManagedPolicy AWS::IAM::Policy AWS::IAM::Role AWS::IAM::User AWS::IAM::UserToGroupAddition 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 Perform custom processing on CloudFormation templates with template macros. Only one of the Capabilities and ResourceType parameters can be specified.
description: 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 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. AWS::IAM::AccessKey AWS::IAM::Group AWS::IAM::InstanceProfile AWS::IAM::ManagedPolicy AWS::IAM::Policy AWS::IAM::Role AWS::IAM::User AWS::IAM::UserToGroupAddition 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 Perform custom processing on CloudFormation templates with template macros. Only one of the Capabilities and ResourceType parameters can be specified.
- name: ResourceTypes
value: "{{ ResourceTypes }}"
description: Specifies which resource types you can work with, such as AWS::EC2::Instance or Custom::MyCustomInstance. 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. IAM uses this parameter for CloudFormation-specific condition keys in IAM policies. For more information, see Control CloudFormation access with Identity and Access Management. Only one of the Capabilities and ResourceType parameters can be specified.
description: Specifies which resource types you can work with, such as AWS::EC2::Instance or Custom::MyCustomInstance. 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. IAM uses this parameter for CloudFormation-specific condition keys in IAM policies. For more information, see Control CloudFormation access with Identity and Access Management. Only one of the Capabilities and ResourceType parameters can be specified.
- name: RoleARN
value: "{{ RoleARN }}"
description: The Amazon Resource Name (ARN) of an 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.
description: The Amazon Resource Name (ARN) of an 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.
- name: OnFailure
value: "{{ OnFailure }}"
description: 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. Although the default setting is ROLLBACK, there is one exception. This exception occurs when a StackSet attempts to deploy a stack instance and the stack instance fails to create successfully. In this case, the CreateStack call overrides the default setting and sets the value of OnFailure to DELETE. Default: ROLLBACK
description: 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. Although the default setting is ROLLBACK, there is one exception. This exception occurs when a StackSet attempts to deploy a stack instance and the stack instance fails to create successfully. In this case, the CreateStack call overrides the default setting and sets the value of OnFailure to DELETE. Default: ROLLBACK
- name: StackPolicyBody
value: "{{ StackPolicyBody }}"
description: Structure that contains the stack policy body. For more information, see Prevent updates to stack resources in the CloudFormation User Guide. You can specify either the StackPolicyBody or the StackPolicyURL parameter, but not both.
description: Structure that contains the stack policy body. For more information, see Prevent updates to stack resources in the CloudFormation User Guide. You can specify either the StackPolicyBody or the StackPolicyURL parameter, but not both.
- name: StackPolicyURL
value: "{{ StackPolicyURL }}"
description: Location of a file that contains 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. The location for an Amazon S3 bucket must start with https://. URLs from S3 static websites are not supported. You can specify either the StackPolicyBody or the StackPolicyURL parameter, but not both.
description: Location of a file that contains 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. The location for an Amazon S3 bucket must start with https://. URLs from S3 static websites are not supported. You can specify either the StackPolicyBody or the StackPolicyURL parameter, but not both.
- name: Tags
value: "{{ Tags }}"
description: 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.
description: 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.
- name: ClientRequestToken
value: "{{ ClientRequestToken }}"
description: 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.
description: 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.
- name: EnableTerminationProtection
value: {{ EnableTerminationProtection }}
description: 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 Protect CloudFormation stacks 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.
description: 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 Protect CloudFormation stacks 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.
- name: RetainExceptOnCreate
value: {{ RetainExceptOnCreate }}
description: When set to true, newly created resources are deleted when the operation rolls back. This includes newly created resources marked with a deletion policy of Retain. Default: false
description: When set to true, newly created resources are deleted when the operation rolls back. This includes newly created resources marked with a deletion policy of Retain. Default: false
- name: DeploymentConfig
value: "{{ DeploymentConfig }}"
description: The deployment configuration for this stack operation, including the deployment mode.
description: The deployment configuration for this stack operation, including the deployment mode.
- name: DisableValidation
value: {{ DisableValidation }}
description: Set to true to disable pre-deployment validations in changeset or stack operations. Default: false
description: Set to true to disable pre-deployment validations in changeset or stack operations. Default: false
UPDATE examples
- update_termination_protection
- update_stack
Updates termination protection for 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 Protect a CloudFormation stack from being deleted in the CloudFormation User Guide. For nested stacks, termination protection is set on the root stack and can't be changed directly on the nested stack.
UPDATE aws.cloudformation.stacks
SET
-- No updatable properties
WHERE
EnableTerminationProtection = '{{ EnableTerminationProtection }}' --required
AND StackName = '{{ StackName }}' --required
AND region = '{{ region }}' --required
RETURNING
line_items;
Updates a stack as specified in the template. After the call completes successfully, the stack update starts. You can check the status of the stack through the DescribeStacks action. To get a copy of the template for an existing stack, you can use the GetTemplate action. For more information about updating a stack and monitoring the progress of the update, see Managing Amazon Web Services resources as a single unit with CloudFormation stacks in the CloudFormation User Guide.
UPDATE aws.cloudformation.stacks
SET
-- No updatable properties
WHERE
StackName = '{{ StackName }}' --required
AND region = '{{ region }}' --required
AND TemplateBody = '{{ TemplateBody}}'
AND TemplateURL = '{{ TemplateURL}}'
AND UsePreviousTemplate = {{ UsePreviousTemplate}}
AND StackPolicyDuringUpdateBody = '{{ StackPolicyDuringUpdateBody}}'
AND StackPolicyDuringUpdateURL = '{{ StackPolicyDuringUpdateURL}}'
AND Parameters = '{{ Parameters}}'
AND Capabilities = '{{ Capabilities}}'
AND ResourceTypes = '{{ ResourceTypes}}'
AND RoleARN = '{{ RoleARN}}'
AND RollbackConfiguration = '{{ RollbackConfiguration}}'
AND StackPolicyBody = '{{ StackPolicyBody}}'
AND StackPolicyURL = '{{ StackPolicyURL}}'
AND NotificationARNs = '{{ NotificationARNs}}'
AND Tags = '{{ Tags}}'
AND DisableRollback = {{ DisableRollback}}
AND ClientRequestToken = '{{ ClientRequestToken}}'
AND RetainExceptOnCreate = {{ RetainExceptOnCreate}}
AND DeploymentConfig = '{{ DeploymentConfig}}'
AND DisableValidation = {{ DisableValidation}}
RETURNING
line_items;
DELETE examples
- delete_stack
Deletes a specified stack. Once the call completes successfully, stack deletion starts. Deleted stacks don't show up in the DescribeStacks operation if the deletion has been completed successfully. For more information about deleting a stack, see Delete a stack from the CloudFormation console in the CloudFormation User Guide.
DELETE FROM aws.cloudformation.stacks
WHERE StackName = '{{ StackName }}' --required
AND region = '{{ region }}' --required
AND RetainResources = '{{ RetainResources }}'
AND RoleARN = '{{ RoleARN }}'
AND ClientRequestToken = '{{ ClientRequestToken }}'
AND DeletionMode = '{{ DeletionMode }}'
AND DeploymentConfig = '{{ DeploymentConfig }}'
;
Lifecycle Methods
- cancel_update_stack
- continue_update_rollback
- detect_stack_drift
- detect_stack_resource_drift
- import_stacks_to_stack_set
- rollback_stack
- signal_resource
Cancels an update on the specified stack. If the call completes successfully, the stack rolls back the update and reverts to the previous stack configuration. You can cancel only stacks that are in the UPDATE_IN_PROGRESS state.
EXEC aws.cloudformation.stacks.cancel_update_stack
@StackName='{{ StackName }}' --required,
@region='{{ region }}' --required,
@ClientRequestToken='{{ ClientRequestToken }}'
;
Continues rolling back a stack from UPDATE_ROLLBACK_FAILED to UPDATE_ROLLBACK_COMPLETE state. Depending on the cause of the failure, you can manually fix the error and continue the rollback. By continuing the rollback, you can return your stack to a working state (the UPDATE_ROLLBACK_COMPLETE state) and then try to update the stack again. A stack enters the UPDATE_ROLLBACK_FAILED state when CloudFormation can't roll back all changes after a failed stack update. For example, this might occur when a stack attempts to roll back to an old database that was deleted outside of CloudFormation. Because CloudFormation doesn't know the instance was deleted, it assumes the instance still exists and attempts to roll back to it, causing the update rollback to fail. For more information, see Continue rolling back an update in the CloudFormation User Guide. For information for troubleshooting a failed update rollback, see Update rollback failed.
EXEC aws.cloudformation.stacks.continue_update_rollback
@StackName='{{ StackName }}' --required,
@region='{{ region }}' --required,
@RoleARN='{{ RoleARN }}',
@ResourcesToSkip='{{ ResourcesToSkip }}',
@ClientRequestToken='{{ ClientRequestToken }}'
;
Detects whether a stack's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. For each resource in the stack that supports drift detection, CloudFormation compares the actual configuration of the resource with its expected template configuration. Only resource properties explicitly defined in the stack template are checked for drift. A stack is considered to have drifted if one or more of its resources differ from their expected template configurations. For more information, see Detect unmanaged configuration changes to stacks and resources with drift detection. Use DetectStackDrift to detect drift on all supported resources for a given stack, or DetectStackResourceDrift to detect drift on individual resources. For a list of stack resources that currently support drift detection, see Resource type support for imports and drift detection. DetectStackDrift can take up to several minutes, depending on the number of resources contained within the stack. Use DescribeStackDriftDetectionStatus to monitor the progress of a detect stack drift operation. Once the drift detection operation has completed, use DescribeStackResourceDrifts to return drift information about the stack and its resources. When detecting drift on a stack, CloudFormation doesn't detect drift on any nested stacks belonging to that stack. Perform DetectStackDrift directly on the nested stack itself.
EXEC aws.cloudformation.stacks.detect_stack_drift
@StackName='{{ StackName }}' --required,
@region='{{ region }}' --required,
@LogicalResourceIds='{{ LogicalResourceIds }}'
;
Returns information about whether a resource's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. This information includes actual and expected property values for resources in which CloudFormation detects drift. Only resource properties explicitly defined in the stack template are checked for drift. For more information about stack and resource drift, see Detect unmanaged configuration changes to stacks and resources with drift detection. Use DetectStackResourceDrift to detect drift on individual resources, or DetectStackDrift to detect drift on all resources in a given stack that support drift detection. Resources that don't currently support drift detection can't be checked. For a list of resources that support drift detection, see Resource type support for imports and drift detection.
EXEC aws.cloudformation.stacks.detect_stack_resource_drift
@StackName='{{ StackName }}' --required,
@LogicalResourceId='{{ LogicalResourceId }}' --required,
@region='{{ region }}' --required
;
Import existing stacks into a new StackSets. Use the stack import operation to import up to 10 stacks into a new StackSet in the same account as the source stack or in a different administrator account and Region, by specifying the stack ID of the stack you intend to import.
EXEC aws.cloudformation.stacks.import_stacks_to_stack_set
@StackSetName='{{ StackSetName }}' --required,
@region='{{ region }}' --required,
@StackIds='{{ StackIds }}',
@StackIdsUrl='{{ StackIdsUrl }}',
@OrganizationalUnitIds='{{ OrganizationalUnitIds }}',
@OperationPreferences='{{ OperationPreferences }}',
@OperationId='{{ OperationId }}',
@CallAs='{{ CallAs }}'
;
When specifying RollbackStack, you preserve the state of previously provisioned resources when an operation fails. You can check the status of the stack through the DescribeStacks operation. Rolls back the specified stack to the last known stable state from CREATE_FAILED or UPDATE_FAILED stack statuses. This operation will delete a stack if it doesn't contain a last known stable state. A last known stable state includes any status in a *_COMPLETE. This includes the following stack statuses. CREATE_COMPLETE UPDATE_COMPLETE UPDATE_ROLLBACK_COMPLETE IMPORT_COMPLETE IMPORT_ROLLBACK_COMPLETE
EXEC aws.cloudformation.stacks.rollback_stack
@StackName='{{ StackName }}' --required,
@region='{{ region }}' --required,
@RoleARN='{{ RoleARN }}',
@ClientRequestToken='{{ ClientRequestToken }}',
@RetainExceptOnCreate={{ RetainExceptOnCreate }},
@DeploymentConfig='{{ DeploymentConfig }}'
;
Sends a signal to the specified resource with a success or failure status. You can use the SignalResource operation in conjunction with a creation policy or update policy. CloudFormation doesn't proceed with a stack creation or update until resources receive the required number of signals or the timeout period is exceeded. The SignalResource operation is useful in cases where you want to send signals from anywhere other than an Amazon EC2 instance.
EXEC aws.cloudformation.stacks.signal_resource
@StackName='{{ StackName }}' --required,
@LogicalResourceId='{{ LogicalResourceId }}' --required,
@UniqueId='{{ UniqueId }}' --required,
@region='{{ region }}' --required,
@Status='{{ Status }}'
;