Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateAutoScalingConfigurationRequest

import type { CreateAutoScalingConfigurationRequest } from "https://aws-api.deno.dev/v0.4/services/apprunner.ts?docs=full";
interface CreateAutoScalingConfigurationRequest {
AutoScalingConfigurationName: string;
MaxConcurrency?: number | null;
MaxSize?: number | null;
MinSize?: number | null;
Tags?: Tag[] | null;
}

§Properties

§
AutoScalingConfigurationName: string
[src]

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.

Note: 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?: number | null
[src]

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

§
MaxSize?: number | null
[src]

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

Default: 25

§
MinSize?: number | null
[src]

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

§
Tags?: Tag[] | null
[src]

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