Creates an application.
See https://www.paws-r-sdk.com/docs/emrserverless_create_application/ for full documentation.
emrserverless_create_application(
name = NULL,
releaseLabel,
type,
clientToken,
initialCapacity = NULL,
maximumCapacity = NULL,
tags = NULL,
autoStartConfiguration = NULL,
autoStopConfiguration = NULL,
networkConfiguration = NULL,
architecture = NULL,
imageConfiguration = NULL,
workerTypeSpecifications = NULL,
runtimeConfiguration = NULL,
monitoringConfiguration = NULL,
interactiveConfiguration = NULL
)The name of the application.
[required] The Amazon EMR release associated with the application.
[required] The type of application you want to start, such as Spark or Hive.
[required] The client idempotency token of the application to create. Its value must be unique for each request.
The capacity to initialize when the application is created.
The maximum capacity to allocate when the application is created. This is cumulative across all workers at any given point in time, not just when an application is created. No new resources will be created once any one of the defined limits is hit.
The tags assigned to the application.
The configuration for an application to automatically start on job submission.
The configuration for an application to automatically stop after a certain amount of time being idle.
The network configuration for customer VPC connectivity.
The CPU architecture of an application.
The image configuration for all worker types. You can either set this
parameter or imageConfiguration for each worker type in
workerTypeSpecifications.
The key-value pairs that specify worker type to
WorkerTypeSpecificationInput. This parameter must contain all valid
worker types for a Spark or Hive application. Valid worker types include
Driver and Executor for Spark applications and HiveDriver and
TezTask for Hive applications. You can either set image details in
this parameter for each worker type, or in imageConfiguration for all
worker types.
The Configuration specifications to use when creating an application. Each configuration consists of a classification and properties. This configuration is applied to all the job runs submitted under the application.
The configuration setting for monitoring.
The interactive configuration object that enables the interactive use cases to use when running an application.