The task placement strategy for a task or service.
Type: objectProperties: 2
Amazon Web ServicesCronEvent-DrivenSchedulingServerless
PlacementStrategy is a JSON Structure definition published by Amazon EventBridge Scheduler, describing 2 properties. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.
{
"$schema": "https://json-structure.org/meta/core/v0/#",
"$id": "https://raw.githubusercontent.com/api-evangelist/amazon-eventbridge-scheduler/refs/heads/main/json-structure/amazon-eventbridge-scheduler-placement-strategy-structure.json",
"name": "PlacementStrategy",
"description": "The task placement strategy for a task or service.",
"type": "object",
"properties": {
"field": {
"allOf": [
{
"$ref": "#/components/schemas/PlacementStrategyField"
},
{
"description": "The field to apply the placement strategy against. For the spread placement strategy, valid values are <code>instanceId</code> (or <code>instanceId</code>, which has the same effect), or any platform or custom attribute that is applied to a container instance, such as <code>attribute:ecs.availability-zone</code>. For the binpack placement strategy, valid values are <code>cpu</code> and <code>memory</code>. For the random placement strategy, this field is not used."
}
]
},
"type": {
"allOf": [
{
"$ref": "#/components/schemas/PlacementStrategyType"
},
{
"description": "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 is 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)."
}
]
}
}
}
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.