Interface CreateAutoScalingConfigurationRequest.Builder

All Superinterfaces:
AppRunnerRequest.Builder, AwsRequest.Builder, Buildable, CopyableBuilder<CreateAutoScalingConfigurationRequest.Builder,CreateAutoScalingConfigurationRequest>, SdkBuilder<CreateAutoScalingConfigurationRequest.Builder,CreateAutoScalingConfigurationRequest>, SdkPojo, SdkRequest.Builder
Enclosing class:
CreateAutoScalingConfigurationRequest

  • Method Details

    • autoScalingConfigurationName

      CreateAutoScalingConfigurationRequest.Builder autoScalingConfigurationName(String 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 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.

      Parameters:
      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 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.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • 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

      Parameters:
      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

      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • 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

      Parameters:
      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

      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • maxSize

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

      Default: 25

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

      Default: 25

      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • tags

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

      Parameters:
      tags - A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • tags

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

      Parameters:
      tags - A list of metadata items that you can associate with your auto scaling configuration resource. A tag is a key-value pair.
      Returns:
      Returns a reference to this object so that method calls can be chained together.
    • tags

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

      This is a convenience method that creates an instance of the Tag.Builder avoiding the need to create one manually via Tag.builder().

      When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to tags(List<Tag>).

      Parameters:
      tags - a consumer that will call methods on Tag.Builder
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:
    • overrideConfiguration

      Description copied from interface: AwsRequest.Builder
      Add an optional request override configuration.
      Specified by:
      overrideConfiguration in interface AwsRequest.Builder
      Parameters:
      overrideConfiguration - The override configuration.
      Returns:
      This object for method chaining.
    • overrideConfiguration

      Description copied from interface: AwsRequest.Builder
      Add an optional request override configuration.
      Specified by:
      overrideConfiguration in interface AwsRequest.Builder
      Parameters:
      builderConsumer - A Consumer to which an empty AwsRequestOverrideConfiguration.Builder will be given.
      Returns:
      This object for method chaining.