Create an App Runner automatic scaling configuration resource. App Runner requires this resource when you create or update App Runner services and you require non-default auto scaling settings. You can share an auto scaling configuration across multiple services.
See https://www.paws-r-sdk.com/docs/apprunner_create_auto_scaling_configuration/ for full documentation.
apprunner_create_auto_scaling_configuration(
AutoScalingConfigurationName,
MaxConcurrency = NULL,
MinSize = NULL,
MaxSize = NULL,
Tags = NULL
)[required] 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
DefaultConfiguration was created.
If you delete the auto scaling configuration you can create another
custom auto scaling configuration with the same
DefaultConfiguration name. The original DefaultConfiguration
resource provided by App Runner remains in your account unless you
make changes to it.
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
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
The maximum number of instances that your service scales up to. At most
MaxSize instances actively serve traffic for your service.
Default: 25
A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.