---
title: "PATCH /deploymentstrategies/{DeploymentStrategyId}"
method: PATCH
path: "/deploymentstrategies/{DeploymentStrategyId}"
---

# PATCH /deploymentstrategies/{DeploymentStrategyId}

`PATCH /deploymentstrategies/{DeploymentStrategyId}`

Updates a deployment strategy.

## Path parameters

- `DeploymentStrategyId` string, required

## Request body

- object
  - `Description` string — A description of the deployment strategy.
  - `DeploymentDurationInMinutes` integer — Total amount of time for a deployment to last.
  - `FinalBakeTimeInMinutes` integer — The amount of time that AppConfig monitors for alarms before considering the deployment to be complete and no longer eligible for automatic rollback.
  - `GrowthFactor` number, float — The percentage of targets to receive a deployed configuration during each interval.
  - `GrowthType` 'LINEAR' | 'EXPONENTIAL' — <p>The algorithm used to define how percentage grows over time. AppConfig supports the following growth types:</p> <p> <b>Linear</b>: For this type, AppConfig processes the deployment by increments of the growth factor evenly distributed over the deployment time. For example, a linear deployment that uses a growth factor of 20 initially makes the configuration available to 20 percent of the targets. After 1/5th of the deployment time has passed, the system updates the percentage to 40 percent. This continues until 100% of the targets are set to receive the deployed configuration.</p> <p> <b>Exponential</b>: For this type, AppConfig processes the deployment exponentially using the following formula: <code>G*(2^N)</code>. In this formula, <code>G</code> is the growth factor specified by the user and <code>N</code> is the number of steps until the configuration is deployed to all targets. For example, if you specify a growth factor of 2, then the system rolls out the configuration as follows:</p> <p> <code>2*(2^0)</code> </p> <p> <code>2*(2^1)</code> </p> <p> <code>2*(2^2)</code> </p> <p>Expressed numerically, the deployment rolls out as follows: 2% of the targets, 4% of the targets, 8% of the targets, and continues until the configuration has been deployed to all targets.</p>

## Response `200`

Success

- DeploymentStrategy
  - `Id` string — The deployment strategy ID.
  - `Name` string — The name of the deployment strategy.
  - `Description` string — The description of the deployment strategy.
  - `DeploymentDurationInMinutes` integer — Total amount of time the deployment lasted.
  - `GrowthType` 'LINEAR' | 'EXPONENTIAL' — The algorithm used to define how percentage grew over time.
  - `GrowthFactor` number, float — The percentage of targets that received a deployed configuration during each interval.
  - `FinalBakeTimeInMinutes` integer — The amount of time that AppConfig monitored for alarms before considering the deployment to be complete and no longer eligible for automatic rollback.
  - `ReplicateTo` 'NONE' | 'SSM_DOCUMENT' — Save the deployment strategy to a Systems Manager (SSM) document.

## Other responses

- `480` — BadRequestException
- `481` — ResourceNotFoundException
- `482` — InternalServerException

---

[API](https://skmtc.net/aws/apis/appconfig.md) · [All operations](https://skmtc.net/aws/apis/appconfig/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/appconfig/versions/924584438718/schema)
