AWS AppConfig Deployment Strategy

This page shows how to write Terraform and CloudFormation for AppConfig Deployment Strategy and write them securely.

aws_appconfig_deployment_strategy (Terraform)

The Deployment Strategy in AppConfig can be configured in Terraform with the resource name aws_appconfig_deployment_strategy. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub

config.tf#L39
resource "aws_appconfig_deployment_strategy" "this" {
  name                           = "immediate"
  deployment_duration_in_minutes = 0
  growth_factor                  = 100
  growth_type                    = "LINEAR"
  replicate_to                   = "NONE"

Review your Terraform file for AWS best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

The following arguments are supported:

  • deployment_duration_in_minutes - (Required) Total amount of time for a deployment to last. Minimum value of 0, maximum value of 1440.
  • growth_factor - (Required) The percentage of targets to receive a deployed configuration during each interval. Minimum value of 1.0, maximum value of 100.0.
  • name - (Required, Forces new resource) A name for the deployment strategy. Must be between 1 and 64 characters in length.
  • replicate_to - (Required, Forces new resource) Where to save the deployment strategy. Valid values: NONE and SSM_DOCUMENT.
  • description - (Optional) A description of the deployment strategy. Can be at most 1024 characters.
  • final_bake_time_in_minutes - (Optional) The amount of time AWS AppConfig monitors for alarms before considering the deployment to be complete and no longer eligible for automatic roll back. Minimum value of 0, maximum value of 1440.
  • growth_type - (Optional) The algorithm used to define how percentage grows over time. Valid value: LINEAR and EXPONENTIAL. Defaults to LINEAR.
  • tags - (Optional) A map of tags to assign to the resource. If configured with a provider default_tags configuration block present, tags with matching keys will overwrite those defined at the provider-level.

In addition to all arguments above, the following attributes are exported:

  • id - The AppConfig deployment strategy ID.
  • arn - The Amazon Resource Name (ARN) of the AppConfig Deployment Strategy.
  • tags_all - A map of tags assigned to the resource, including those inherited from the provider default_tags configuration block.

Explanation in Terraform Registry

Provides an AppConfig Deployment Strategy resource.

AWS::AppConfig::DeploymentStrategy (CloudFormation)

The DeploymentStrategy in AppConfig can be configured in CloudFormation with the resource name AWS::AppConfig::DeploymentStrategy. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Parameters

Explanation in CloudFormation Registry

The AWS::AppConfig::DeploymentStrategy resource creates an AWS AppConfig deployment strategy. A deployment strategy defines important criteria for rolling out your configuration to the designated targets. A deployment strategy includes: the overall duration required, a percentage of targets to receive the deployment during each interval, an algorithm that defines how percentage grows, and bake time.

AWS AppConfig requires that you create resources and deploy a configuration in the following order:1. Create an application1. Create an environment1. Create a configuration profile1. Create a deployment strategy1. Deploy the configurationFor more information, see AWS AppConfig in the AWS AppConfig User Guide.

Frequently asked questions

What is AWS AppConfig Deployment Strategy?

AWS AppConfig Deployment Strategy is a resource for AppConfig of Amazon Web Service. Settings can be wrote in Terraform and CloudFormation.

Where can I find the example code for the AWS AppConfig Deployment Strategy?

For Terraform, the easyas314159/lobbyboy source code example is useful. See the Terraform Example section for further details.