CreateAutoScalingConfigurationRequest
¶
Source code in docs_src/capo_apprunner/types/create_auto_scaling_configuration_request.py
auto_scaling_configuration_name
instance-attribute
¶
auto_scaling_configuration_name: AutoScalingConfigurationName
A name for the auto scaling configuration. When you use it for the first time in an Amazon Web Services Region, App Runner creates revision number 1 of this name. When you use the same name in subsequent calls, App Runner creates incremental revisions of the configuration.
Prior to the release of Auto scale configuration enhancements, the name DefaultConfiguration was reserved.
This restriction is no longer in place. You can now manage DefaultConfiguration the same way you manage your custom auto scaling configurations. This means you can do the following with the DefaultConfiguration that App Runner provides:
-
Create new revisions of the
DefaultConfiguration. -
Delete the revisions of the
DefaultConfiguration. -
Delete the auto scaling configuration for which the App Runner
DefaultConfigurationwas created. -
If you delete the auto scaling configuration you can create another custom auto scaling configuration with the same
DefaultConfigurationname. The originalDefaultConfigurationresource provided by App Runner remains in your account unless you make changes to it.
max_concurrency
instance-attribute
¶
max_concurrency: NotRequired[ASConfigMaxConcurrency]
The maximum number of concurrent requests that you want an instance to process. If the number of concurrent requests exceeds this limit, App Runner scales up your service.
Default: 100
max_size
instance-attribute
¶
max_size: NotRequired[ASConfigMaxSize]
The maximum number of instances that your service scales up to. At most MaxSize instances actively serve traffic for your service.
Default: 25
min_size
instance-attribute
¶
min_size: NotRequired[ASConfigMinSize]
The minimum number of instances that App Runner provisions for your service. The service always has at least MinSize provisioned instances. Some of them actively serve traffic. The rest of them (provisioned and inactive instances) are a cost-effective compute capacity reserve and are ready to be quickly activated. You pay for memory usage of all the provisioned instances. You pay for CPU usage of only the active subset.
App Runner temporarily doubles the number of provisioned instances during deployments, to maintain the same capacity for both old and new code.
Default: 1