apprunner_create_auto_scaling_configuration: Create an App Runner automatic scaling configuration resource

View source: R/apprunner_operations.R

apprunner_create_auto_scaling_configurationR Documentation

Create an App Runner automatic scaling configuration resource

Description

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.

Usage

apprunner_create_auto_scaling_configuration(
  AutoScalingConfigurationName,
  MaxConcurrency = NULL,
  MinSize = NULL,
  MaxSize = NULL,
  Tags = NULL
)

Arguments

AutoScalingConfigurationName

[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.

The name DefaultConfiguration is reserved (it's the configuration that App Runner uses if you don't provide a custome one). You can't use it to create a new auto scaling configuration, and you can't create a revision of it.

When you want to use your own auto scaling configuration for your App Runner service, create a configuration with a different name, and then provide it when you create or update your service.

MaxConcurrency

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

MinSize

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

MaxSize

The maximum number of instances that your service scales up to. At most MaxSize instances actively serve traffic for your service.

Default: 25

Tags

A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.


paws.compute documentation built on Sept. 12, 2023, 1:28 a.m.