DeploymentConfiguration

Diese Seite wurde nicht in Ihre Sprache übersetzt. Übersetzung anfragen

Set of rules for processing a deployment for a container fleet update.

Contents

Note

In the following list, the required parameters are described first.

ImpairmentStrategy

Determines what actions to take if a deployment fails. If the fleet is multi-location, this strategy applies across all fleet locations. With a rollback strategy, updated fleet instances are rolled back to the last successful deployment. Alternatively, you can maintain a few impaired containers for the purpose of debugging, while all other tasks return to the last successful deployment.

Type: String

Valid Values: MAINTAIN | ROLLBACK

Required: No

MinimumHealthyPercentage

Sets a minimum level of healthy tasks to maintain during deployment activity.

Type: Integer

Valid Range: Minimum value of 30. Maximum value of 75.

Required: No

ProtectionStrategy

Determines how fleet deployment activity affects active game sessions on the fleet. With protection, a deployment honors game session protection, and delays actions that would interrupt a protected active game session until the game session ends. Without protection, deployment activity can shut down all running tasks, including active game sessions, regardless of game session protection.

Type: String

Valid Values: WITH_PROTECTION | IGNORE_PROTECTION

Required: No

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following:

• AWS SDK for C++

• AWS SDK for Java V2

• AWS SDK for Ruby V3