| Copyright | (c) 2013-2023 Brendan Hay |
|---|---|
| License | Mozilla Public License, v. 2.0. |
| Maintainer | Brendan Hay |
| Stability | auto-generated |
| Portability | non-portable (GHC extensions) |
| Safe Haskell | Safe-Inferred |
| Language | Haskell2010 |
Amazonka.ECS.Types.PlacementStrategy
Description
Documentation
data PlacementStrategy Source #
The task placement strategy for a task or service. For more information, see Task placement strategies in the Amazon Elastic Container Service Developer Guide.
See: newPlacementStrategy smart constructor.
Constructors
| PlacementStrategy' | |
Fields
| |
Instances
newPlacementStrategy :: PlacementStrategy Source #
Create a value of PlacementStrategy with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:field:PlacementStrategy', placementStrategy_field - The field to apply the placement strategy against. For the spread
placement strategy, valid values are instanceId (or host, which has
the same effect), or any platform or custom attribute that's applied to
a container instance, such as attribute:ecs.availability-zone. For the
binpack placement strategy, valid values are cpu and memory. For
the random placement strategy, this field is not used.
$sel:type':PlacementStrategy', placementStrategy_type - The type of placement strategy. The random placement strategy randomly
places tasks on available candidates. The spread placement strategy
spreads placement across available candidates evenly based on the
field parameter. The binpack strategy places tasks on available
candidates that have the least available amount of the resource that's
specified with the field parameter. For example, if you binpack on
memory, a task is placed on the instance with the least amount of
remaining memory but still enough to run the task.
placementStrategy_field :: Lens' PlacementStrategy (Maybe Text) Source #
The field to apply the placement strategy against. For the spread
placement strategy, valid values are instanceId (or host, which has
the same effect), or any platform or custom attribute that's applied to
a container instance, such as attribute:ecs.availability-zone. For the
binpack placement strategy, valid values are cpu and memory. For
the random placement strategy, this field is not used.
placementStrategy_type :: Lens' PlacementStrategy (Maybe PlacementStrategyType) Source #
The type of placement strategy. The random placement strategy randomly
places tasks on available candidates. The spread placement strategy
spreads placement across available candidates evenly based on the
field parameter. The binpack strategy places tasks on available
candidates that have the least available amount of the resource that's
specified with the field parameter. For example, if you binpack on
memory, a task is placed on the instance with the least amount of
remaining memory but still enough to run the task.