App-FargateStack
view release on metacpan or search on metacpan
- **max\_capacity** (Required)
The maximum number of tasks that the service can scale out to. This acts as
a safeguard to control costs.
- **cpu** OR **requests** (Required, mutually exclusive)
You must specify exactly one scaling metric.
- `cpu`: The target average CPU utilization percentage across all tasks in
the service. Valid values are between 1 and 100.
- `requests`: The target number of requests per minute for each task. This
is only valid for tasks of type `http` or `https` that are behind an
Application Load Balancer.
- **scale\_in\_cooldown** (Optional)
The amount of time, in seconds, to wait after a scale-in activity before
another scale-in activity can start. This prevents the service from scaling
in too aggressively.
lib/App/FargateStack/Pod.pm view on Meta::CPAN
The maximum number of tasks that the service can scale out to. This acts as
a safeguard to control costs.
=item * B<cpu> OR B<requests> (Required, mutually exclusive)
You must specify exactly one scaling metric.
=over
=item * C<cpu>: The target average CPU utilization percentage across all tasks in
the service. Valid values are between 1 and 100.
=item * C<requests>: The target number of requests per minute for each task. This
is only valid for tasks of type C<http> or C<https> that are behind an
Application Load Balancer.
=back
=item * B<scale_in_cooldown> (Optional)
share/README.md view on Meta::CPAN
- **max\_capacity** (Required)
The maximum number of tasks that the service can scale out to. This acts as
a safeguard to control costs.
- **cpu** OR **requests** (Required, mutually exclusive)
You must specify exactly one scaling metric.
- `cpu`: The target average CPU utilization percentage across all tasks in
the service. Valid values are between 1 and 100.
- `requests`: The target number of requests per minute for each task. This
is only valid for tasks of type `http` or `https` that are behind an
Application Load Balancer.
- **scale\_in\_cooldown** (Optional)
The amount of time, in seconds, to wait after a scale-in activity before
another scale-in activity can start. This prevents the service from scaling
in too aggressively.
( run in 1.255 second using v1.01-cache-2.11-cpan-39bf76dae61 )