| Server IP : 195.201.23.43 / Your IP : 3.15.0.42 Web Server : Apache System : Linux webserver2.vercom.be 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 User : kdecoratie ( 1041) PHP Version : 7.1.33-63+ubuntu20.04.1+deb.sury.org+1 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /lib/python3/dist-packages/awscli/examples/opsworks/ |
Upload File : |
**To describe a layer's load-based scaling configuration**
The following example describes a specified layer's load-based scaling configuration.
The layer is identified by its layer ID, which you can find on the layer's
details page or by running ``describe-layers``. ::
aws opsworks describe-load-based-auto-scaling --region us-east-1 --layer-ids 6bec29c9-c866-41a0-aba5-fa3e374ce2a1
*Output*: The example layer has a single load-based instance. ::
{
"LoadBasedAutoScalingConfigurations": [
{
"DownScaling": {
"IgnoreMetricsTime": 10,
"ThresholdsWaitTime": 10,
"InstanceCount": 1,
"CpuThreshold": 30.0
},
"Enable": true,
"UpScaling": {
"IgnoreMetricsTime": 5,
"ThresholdsWaitTime": 5,
"InstanceCount": 1,
"CpuThreshold": 80.0
},
"LayerId": "6bec29c9-c866-41a0-aba5-fa3e374ce2a1"
}
]
}
**More Information**
For more information, see `How Automatic Load-based Scaling Works`_ in the *AWS OpsWorks User Guide*.
.. _`How Automatic Load-based Scaling Works`: http://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-autoscaling.html#workinginstances-autoscaling-loadbased
Private