From 9a4e1431515ef4d12cdfe747c495fcf28d4ad41e Mon Sep 17 00:00:00 2001
From: awstools Amazon EMR on EKS provides a deployment option for Amazon EMR that allows
you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).
With this deployment option, you can focus on running analytics workloads while Amazon EMR on EKS builds, configures, and manages containers for open-source applications.
-For more information about Amazon EMR on EKS concepts and tasks, see What is
+For more information about Amazon EMR on EKS concepts and tasks, see What is
shared id="EMR-EKS"/>.
-Amazon EMR containers is the API name for Amazon EMR on EKS.
-The emr-containers
prefix is used in the following scenarios: emr-containers
prefix is used in the following
+scenarios:
It is the prefix in the CLI commands for Amazon EMR on EKS. For example, diff --git a/clients/client-emr-containers/src/EMRContainers.ts b/clients/client-emr-containers/src/EMRContainers.ts index 685d65e725ea..c6bb7c938d2b 100644 --- a/clients/client-emr-containers/src/EMRContainers.ts +++ b/clients/client-emr-containers/src/EMRContainers.ts @@ -429,11 +429,11 @@ export interface EMRContainers { *
Amazon EMR on EKS provides a deployment option for Amazon EMR that allows * you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS). * With this deployment option, you can focus on running analytics workloads while Amazon EMR on EKS builds, configures, and manages containers for open-source applications. - * For more information about Amazon EMR on EKS concepts and tasks, see What is + * For more information about Amazon EMR on EKS concepts and tasks, see What is * shared id="EMR-EKS"/>.
*
- * Amazon EMR containers is the API name for Amazon EMR on EKS.
- * The emr-containers
prefix is used in the following scenarios:
emr-containers
prefix is used in the following
+ * scenarios:
* It is the prefix in the CLI commands for Amazon EMR on EKS. For example, diff --git a/clients/client-emr-containers/src/EMRContainersClient.ts b/clients/client-emr-containers/src/EMRContainersClient.ts index fe7a1e7e238d..31cc19cffdd8 100644 --- a/clients/client-emr-containers/src/EMRContainersClient.ts +++ b/clients/client-emr-containers/src/EMRContainersClient.ts @@ -331,11 +331,11 @@ export interface EMRContainersClientResolvedConfig extends EMRContainersClientRe *
Amazon EMR on EKS provides a deployment option for Amazon EMR that allows * you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS). * With this deployment option, you can focus on running analytics workloads while Amazon EMR on EKS builds, configures, and manages containers for open-source applications. - * For more information about Amazon EMR on EKS concepts and tasks, see What is + * For more information about Amazon EMR on EKS concepts and tasks, see What is * shared id="EMR-EKS"/>.
*
- * Amazon EMR containers is the API name for Amazon EMR on EKS.
- * The emr-containers
prefix is used in the following scenarios:
emr-containers
prefix is used in the following
+ * scenarios:
* It is the prefix in the CLI commands for Amazon EMR on EKS. For example, diff --git a/clients/client-emr-containers/src/commands/CreateManagedEndpointCommand.ts b/clients/client-emr-containers/src/commands/CreateManagedEndpointCommand.ts index f8a925b3c370..dc2cc77776f9 100644 --- a/clients/client-emr-containers/src/commands/CreateManagedEndpointCommand.ts +++ b/clients/client-emr-containers/src/commands/CreateManagedEndpointCommand.ts @@ -40,9 +40,8 @@ export interface CreateManagedEndpointCommandOutput extends CreateManagedEndpoin /** * @public - *
Creates a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to - * Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual - * cluster.
+ *Creates a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can + * communicate with your virtual cluster.
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -83,6 +82,10 @@ export interface CreateManagedEndpointCommandOutput extends CreateManagedEndpoin * s3MonitoringConfiguration: { // S3MonitoringConfiguration * logUri: "STRING_VALUE", // required * }, + * containerLogRotationConfiguration: { // ContainerLogRotationConfiguration + * rotationSize: "STRING_VALUE", // required + * maxFilesToKeep: Number("int"), // required + * }, * }, * }, * clientToken: "STRING_VALUE", // required diff --git a/clients/client-emr-containers/src/commands/DeleteManagedEndpointCommand.ts b/clients/client-emr-containers/src/commands/DeleteManagedEndpointCommand.ts index b74532021547..4ad08f253e12 100644 --- a/clients/client-emr-containers/src/commands/DeleteManagedEndpointCommand.ts +++ b/clients/client-emr-containers/src/commands/DeleteManagedEndpointCommand.ts @@ -36,9 +36,8 @@ export interface DeleteManagedEndpointCommandOutput extends DeleteManagedEndpoin /** * @public - *Deletes a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to - * Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual - * cluster.
+ *Deletes a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can + * communicate with your virtual cluster.
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-emr-containers/src/commands/DescribeJobRunCommand.ts b/clients/client-emr-containers/src/commands/DescribeJobRunCommand.ts index 76194c8fc364..29b703bad705 100644 --- a/clients/client-emr-containers/src/commands/DescribeJobRunCommand.ts +++ b/clients/client-emr-containers/src/commands/DescribeJobRunCommand.ts @@ -91,6 +91,10 @@ export interface DescribeJobRunCommandOutput extends DescribeJobRunResponse, __M * // s3MonitoringConfiguration: { // S3MonitoringConfiguration * // logUri: "STRING_VALUE", // required * // }, + * // containerLogRotationConfiguration: { // ContainerLogRotationConfiguration + * // rotationSize: "STRING_VALUE", // required + * // maxFilesToKeep: Number("int"), // required + * // }, * // }, * // }, * // jobDriver: { // JobDriver diff --git a/clients/client-emr-containers/src/commands/DescribeManagedEndpointCommand.ts b/clients/client-emr-containers/src/commands/DescribeManagedEndpointCommand.ts index 02932ddd3ec4..6135a5ffb15e 100644 --- a/clients/client-emr-containers/src/commands/DescribeManagedEndpointCommand.ts +++ b/clients/client-emr-containers/src/commands/DescribeManagedEndpointCommand.ts @@ -41,8 +41,7 @@ export interface DescribeManagedEndpointCommandOutput extends DescribeManagedEnd /** * @public *Displays detailed information about a managed endpoint. A managed endpoint is a gateway - * that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with - * your virtual cluster.
+ * that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual cluster. * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -97,6 +96,10 @@ export interface DescribeManagedEndpointCommandOutput extends DescribeManagedEnd * // s3MonitoringConfiguration: { // S3MonitoringConfiguration * // logUri: "STRING_VALUE", // required * // }, + * // containerLogRotationConfiguration: { // ContainerLogRotationConfiguration + * // rotationSize: "STRING_VALUE", // required + * // maxFilesToKeep: Number("int"), // required + * // }, * // }, * // }, * // serverUrl: "STRING_VALUE", diff --git a/clients/client-emr-containers/src/commands/ListJobRunsCommand.ts b/clients/client-emr-containers/src/commands/ListJobRunsCommand.ts index 48754d6ebfc9..8145c5f833c1 100644 --- a/clients/client-emr-containers/src/commands/ListJobRunsCommand.ts +++ b/clients/client-emr-containers/src/commands/ListJobRunsCommand.ts @@ -95,6 +95,10 @@ export interface ListJobRunsCommandOutput extends ListJobRunsResponse, __Metadat * // s3MonitoringConfiguration: { // S3MonitoringConfiguration * // logUri: "STRING_VALUE", // required * // }, + * // containerLogRotationConfiguration: { // ContainerLogRotationConfiguration + * // rotationSize: "STRING_VALUE", // required + * // maxFilesToKeep: Number("int"), // required + * // }, * // }, * // }, * // jobDriver: { // JobDriver diff --git a/clients/client-emr-containers/src/commands/ListManagedEndpointsCommand.ts b/clients/client-emr-containers/src/commands/ListManagedEndpointsCommand.ts index f6c33af5e484..797f180dc7a9 100644 --- a/clients/client-emr-containers/src/commands/ListManagedEndpointsCommand.ts +++ b/clients/client-emr-containers/src/commands/ListManagedEndpointsCommand.ts @@ -41,8 +41,7 @@ export interface ListManagedEndpointsCommandOutput extends ListManagedEndpointsR /** * @public *Lists managed endpoints based on a set of parameters. A managed endpoint is a gateway - * that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with - * your virtual cluster.
+ * that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual cluster. * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -107,6 +106,10 @@ export interface ListManagedEndpointsCommandOutput extends ListManagedEndpointsR * // s3MonitoringConfiguration: { // S3MonitoringConfiguration * // logUri: "STRING_VALUE", // required * // }, + * // containerLogRotationConfiguration: { // ContainerLogRotationConfiguration + * // rotationSize: "STRING_VALUE", // required + * // maxFilesToKeep: Number("int"), // required + * // }, * // }, * // }, * // serverUrl: "STRING_VALUE", diff --git a/clients/client-emr-containers/src/commands/StartJobRunCommand.ts b/clients/client-emr-containers/src/commands/StartJobRunCommand.ts index da447994c7be..acfd20642ea0 100644 --- a/clients/client-emr-containers/src/commands/StartJobRunCommand.ts +++ b/clients/client-emr-containers/src/commands/StartJobRunCommand.ts @@ -90,6 +90,10 @@ export interface StartJobRunCommandOutput extends StartJobRunResponse, __Metadat * s3MonitoringConfiguration: { // S3MonitoringConfiguration * logUri: "STRING_VALUE", // required * }, + * containerLogRotationConfiguration: { // ContainerLogRotationConfiguration + * rotationSize: "STRING_VALUE", // required + * maxFilesToKeep: Number("int"), // required + * }, * }, * }, * tags: { // TagMap diff --git a/clients/client-emr-containers/src/commands/TagResourceCommand.ts b/clients/client-emr-containers/src/commands/TagResourceCommand.ts index c335ca2b9716..a9ac4b31677c 100644 --- a/clients/client-emr-containers/src/commands/TagResourceCommand.ts +++ b/clients/client-emr-containers/src/commands/TagResourceCommand.ts @@ -36,14 +36,15 @@ export interface TagResourceCommandOutput extends TagResourceResponse, __Metadat /** * @public - *Assigns tags to resources. A tag is a label that you assign to an Amazon Web Services resource. Each tag - * consists of a key and an optional value, both of which you define. Tags enable you to - * categorize your Amazon Web Services resources by attributes such as purpose, owner, or environment. When - * you have many resources of the same type, you can quickly identify a specific resource - * based on the tags you've assigned to it. For example, you can define a set of tags for your - * Amazon EMR on EKS clusters to help you track each cluster's owner and stack level. - * We recommend that you devise a consistent set of tag keys for each resource type. You can - * then search and filter the resources based on the tags that you add.
+ *Assigns tags to resources. A tag is a label that you assign to an Amazon Web Services + * resource. Each tag consists of a key and an optional value, both of which you define. Tags + * enable you to categorize your Amazon Web Services resources by attributes such as purpose, + * owner, or environment. When you have many resources of the same type, you can quickly + * identify a specific resource based on the tags you've assigned to it. For example, you can + * define a set of tags for your Amazon EMR on EKS clusters to help you track each + * cluster's owner and stack level. We recommend that you devise a consistent set of tag keys + * for each resource type. You can then search and filter the resources based on the tags that + * you add.
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-emr-containers/src/index.ts b/clients/client-emr-containers/src/index.ts index 8cc0c22c6e8b..7f37a62915e0 100644 --- a/clients/client-emr-containers/src/index.ts +++ b/clients/client-emr-containers/src/index.ts @@ -4,11 +4,11 @@ *Amazon EMR on EKS provides a deployment option for Amazon EMR that allows * you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS). * With this deployment option, you can focus on running analytics workloads while Amazon EMR on EKS builds, configures, and manages containers for open-source applications. - * For more information about Amazon EMR on EKS concepts and tasks, see What is + * For more information about Amazon EMR on EKS concepts and tasks, see What is * shared id="EMR-EKS"/>.
*
- * Amazon EMR containers is the API name for Amazon EMR on EKS.
- * The emr-containers
prefix is used in the following scenarios:
emr-containers
prefix is used in the following
+ * scenarios:
* It is the prefix in the CLI commands for Amazon EMR on EKS. For example, diff --git a/clients/client-emr-containers/src/models/models_0.ts b/clients/client-emr-containers/src/models/models_0.ts index c0dcafb04faf..2048316cec04 100644 --- a/clients/client-emr-containers/src/models/models_0.ts +++ b/clients/client-emr-containers/src/models/models_0.ts @@ -272,6 +272,22 @@ export interface CloudWatchMonitoringConfiguration { logStreamNamePrefix?: string; } +/** + * @public + *
The settings for container log rotation.
+ */ +export interface ContainerLogRotationConfiguration { + /** + *The file size at which to rotate logs. Minimum of 2KB, Maximum of 2GB.
+ */ + rotationSize: string | undefined; + + /** + *The number of files to keep in container after rotation.
+ */ + maxFilesToKeep: number | undefined; +} + /** * @public * @enum @@ -317,6 +333,11 @@ export interface MonitoringConfiguration { *Amazon S3 configuration for monitoring log publishing.
*/ s3MonitoringConfiguration?: S3MonitoringConfiguration; + + /** + *Enable or disable container log rotation.
+ */ + containerLogRotationConfiguration?: ContainerLogRotationConfiguration; } /** @@ -408,7 +429,8 @@ export type ContainerProviderType = (typeof ContainerProviderType)[keyof typeof */ export interface ContainerProvider { /** - *The type of the container provider. Amazon EKS is the only supported type as of now.
+ *The type of the container provider. Amazon EKS is the only supported type as of + * now.
*/ type: ContainerProviderType | string | undefined; @@ -697,11 +719,11 @@ export type VirtualClusterState = (typeof VirtualClusterState)[keyof typeof Virt /** * @public *This entity describes a virtual cluster. A virtual cluster is a Kubernetes namespace - * that Amazon EMR is registered with. Amazon EMR uses virtual clusters to run jobs and host - * endpoints. Multiple virtual clusters can be backed by the same physical cluster. However, - * each virtual cluster maps to one namespace on an Amazon EKS cluster. Virtual clusters do not - * create any active resources that contribute to your bill or that require lifecycle - * management outside the service.
+ * that Amazon EMR is registered with. Amazon EMR uses virtual clusters to run + * jobs and host endpoints. Multiple virtual clusters can be backed by the same physical + * cluster. However, each virtual cluster maps to one namespace on an Amazon EKS + * cluster. Virtual clusters do not create any active resources that contribute to your bill + * or that require lifecycle management outside the service. */ export interface VirtualCluster { /** @@ -1001,8 +1023,8 @@ export interface ListVirtualClustersRequest { containerProviderId?: string; /** - *The container provider type of the virtual cluster. Amazon EKS is the only supported type as of - * now.
+ *The container provider type of the virtual cluster. Amazon EKS is the only + * supported type as of now.
*/ containerProviderType?: ContainerProviderType | string; diff --git a/clients/client-emr-containers/src/protocols/Aws_restJson1.ts b/clients/client-emr-containers/src/protocols/Aws_restJson1.ts index de2199be0688..3f8d16200765 100644 --- a/clients/client-emr-containers/src/protocols/Aws_restJson1.ts +++ b/clients/client-emr-containers/src/protocols/Aws_restJson1.ts @@ -77,6 +77,7 @@ import { Configuration, ConfigurationOverrides, ContainerInfo, + ContainerLogRotationConfiguration, ContainerProvider, EksInfo, Endpoint, @@ -1949,6 +1950,8 @@ const se_ConfigurationOverrides = (input: ConfigurationOverrides, context: __Ser // se_ContainerInfo omitted. +// se_ContainerLogRotationConfiguration omitted. + // se_ContainerProvider omitted. // se_EksInfo omitted. @@ -2046,6 +2049,8 @@ const de_ConfigurationOverrides = (output: any, context: __SerdeContext): Config // de_ContainerInfo omitted. +// de_ContainerLogRotationConfiguration omitted. + // de_ContainerProvider omitted. // de_Credentials omitted. diff --git a/codegen/sdk-codegen/aws-models/emr-containers.json b/codegen/sdk-codegen/aws-models/emr-containers.json index 107adf60e7f2..86e8ea93abef 100644 --- a/codegen/sdk-codegen/aws-models/emr-containers.json +++ b/codegen/sdk-codegen/aws-models/emr-containers.json @@ -116,7 +116,7 @@ "name": "emr-containers" }, "aws.protocols#restJson1": {}, - "smithy.api#documentation": "Amazon EMR on EKS provides a deployment option for Amazon EMR that allows\n you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).\n With this deployment option, you can focus on running analytics workloads while Amazon EMR on EKS builds, configures, and manages containers for open-source applications.\n For more information about Amazon EMR on EKS concepts and tasks, see What is\n shared id=\"EMR-EKS\"/>.
\n\n Amazon EMR containers is the API name for Amazon EMR on EKS.\n The emr-containers
prefix is used in the following scenarios:
It is the prefix in the CLI commands for Amazon EMR on EKS. For example,\n aws emr-containers start-job-run
.
It is the prefix before IAM policy actions for Amazon EMR on EKS. For\n example, \"Action\": [ \"emr-containers:StartJobRun\"]
. For more\n information, see Policy actions for Amazon EMR on EKS.
It is the prefix used in Amazon EMR on EKS service endpoints. For example,\n emr-containers.us-east-2.amazonaws.com
. For more information, see\n Amazon EMR on EKSService Endpoints.
Amazon EMR on EKS provides a deployment option for Amazon EMR that allows\n you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).\n With this deployment option, you can focus on running analytics workloads while Amazon EMR on EKS builds, configures, and manages containers for open-source applications.\n For more information about Amazon EMR on EKS concepts and tasks, see What is\n shared id=\"EMR-EKS\"/>.
\n\n Amazon EMR containers is the API name for Amazon EMR on EKS. The emr-containers
prefix is used in the following\n scenarios:
It is the prefix in the CLI commands for Amazon EMR on EKS. For example,\n aws emr-containers start-job-run
.
It is the prefix before IAM policy actions for Amazon EMR on EKS. For\n example, \"Action\": [ \"emr-containers:StartJobRun\"]
. For more\n information, see Policy actions for Amazon EMR on EKS.
It is the prefix used in Amazon EMR on EKS service endpoints. For example,\n emr-containers.us-east-2.amazonaws.com
. For more information, see\n Amazon EMR on EKSService Endpoints.
The information about the container used for a job run or a managed endpoint.
" } }, + "com.amazonaws.emrcontainers#ContainerLogRotationConfiguration": { + "type": "structure", + "members": { + "rotationSize": { + "target": "com.amazonaws.emrcontainers#RotationSize", + "traits": { + "smithy.api#documentation": "The file size at which to rotate logs. Minimum of 2KB, Maximum of 2GB.
", + "smithy.api#required": {} + } + }, + "maxFilesToKeep": { + "target": "com.amazonaws.emrcontainers#MaxFilesToKeep", + "traits": { + "smithy.api#documentation": "The number of files to keep in container after rotation.
", + "smithy.api#required": {} + } + } + }, + "traits": { + "smithy.api#documentation": "The settings for container log rotation.
" + } + }, "com.amazonaws.emrcontainers#ContainerProvider": { "type": "structure", "members": { "type": { "target": "com.amazonaws.emrcontainers#ContainerProviderType", "traits": { - "smithy.api#documentation": "The type of the container provider. Amazon EKS is the only supported type as of now.
", + "smithy.api#documentation": "The type of the container provider. Amazon EKS is the only supported type as of\n now.
", "smithy.api#required": {} } }, @@ -1418,7 +1440,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to\n Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual\n cluster.
", + "smithy.api#documentation": "Creates a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can\n communicate with your virtual cluster.
", "smithy.api#http": { "method": "POST", "uri": "/virtualclusters/{virtualClusterId}/endpoints", @@ -1723,7 +1745,7 @@ } ], "traits": { - "smithy.api#documentation": "Deletes a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to\n Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual\n cluster.
", + "smithy.api#documentation": "Deletes a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can\n communicate with your virtual cluster.
", "smithy.api#http": { "method": "DELETE", "uri": "/virtualclusters/{virtualClusterId}/endpoints/{id}", @@ -1974,7 +1996,7 @@ } ], "traits": { - "smithy.api#documentation": "Displays detailed information about a managed endpoint. A managed endpoint is a gateway\n that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with\n your virtual cluster.
", + "smithy.api#documentation": "Displays detailed information about a managed endpoint. A managed endpoint is a gateway\n that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual cluster.
", "smithy.api#http": { "method": "GET", "uri": "/virtualclusters/{virtualClusterId}/endpoints/{id}", @@ -2836,7 +2858,7 @@ "min": 3, "max": 2048 }, - "smithy.api#pattern": "^(arn:(aws[a-zA-Z0-9-]*):kms:([a-zA-Z0-9]+-?)+:(\\d{12})?:key\\/[(0-9a-zA-Z)-?]+|\\$\\{[a-zA-Z]\\w*\\})$" + "smithy.api#pattern": "^(arn:(aws[a-zA-Z0-9-]*):kms:.+:(\\d{12})?:key\\/[(0-9a-zA-Z)-?]+|\\$\\{[a-zA-Z]\\w*\\})$" } }, "com.amazonaws.emrcontainers#KubernetesNamespace": { @@ -3062,7 +3084,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists managed endpoints based on a set of parameters. A managed endpoint is a gateway\n that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with\n your virtual cluster.
", + "smithy.api#documentation": "Lists managed endpoints based on a set of parameters. A managed endpoint is a gateway\n that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual cluster.
", "smithy.api#http": { "method": "GET", "uri": "/virtualclusters/{virtualClusterId}/endpoints", @@ -3256,7 +3278,7 @@ "containerProviderType": { "target": "com.amazonaws.emrcontainers#ContainerProviderType", "traits": { - "smithy.api#documentation": "The container provider type of the virtual cluster. Amazon EKS is the only supported type as of\n now.
", + "smithy.api#documentation": "The container provider type of the virtual cluster. Amazon EKS is the only\n supported type as of now.
", "smithy.api#httpQuery": "containerProviderType" } }, @@ -3340,6 +3362,15 @@ "smithy.api#pattern": "^[\\.\\-_/#A-Za-z0-9]+$" } }, + "com.amazonaws.emrcontainers#MaxFilesToKeep": { + "type": "integer", + "traits": { + "smithy.api#range": { + "min": 1, + "max": 50 + } + } + }, "com.amazonaws.emrcontainers#MonitoringConfiguration": { "type": "structure", "members": { @@ -3360,6 +3391,12 @@ "traits": { "smithy.api#documentation": "Amazon S3 configuration for monitoring log publishing.
" } + }, + "containerLogRotationConfiguration": { + "target": "com.amazonaws.emrcontainers#ContainerLogRotationConfiguration", + "traits": { + "smithy.api#documentation": "Enable or disable container log rotation.
" + } } }, "traits": { @@ -3589,6 +3626,16 @@ "smithy.api#documentation": "The current status of the retry policy executed on the job.
" } }, + "com.amazonaws.emrcontainers#RotationSize": { + "type": "string", + "traits": { + "smithy.api#length": { + "min": 3, + "max": 12 + }, + "smithy.api#pattern": "^\\d+(\\.\\d+)?[KMG][Bb]?$" + } + }, "com.amazonaws.emrcontainers#RsiArn": { "type": "string", "traits": { @@ -3940,7 +3987,7 @@ } ], "traits": { - "smithy.api#documentation": "Assigns tags to resources. A tag is a label that you assign to an Amazon Web Services resource. Each tag\n consists of a key and an optional value, both of which you define. Tags enable you to\n categorize your Amazon Web Services resources by attributes such as purpose, owner, or environment. When\n you have many resources of the same type, you can quickly identify a specific resource\n based on the tags you've assigned to it. For example, you can define a set of tags for your\n Amazon EMR on EKS clusters to help you track each cluster's owner and stack level.\n We recommend that you devise a consistent set of tag keys for each resource type. You can\n then search and filter the resources based on the tags that you add.
", + "smithy.api#documentation": "Assigns tags to resources. A tag is a label that you assign to an Amazon Web Services\n resource. Each tag consists of a key and an optional value, both of which you define. Tags\n enable you to categorize your Amazon Web Services resources by attributes such as purpose,\n owner, or environment. When you have many resources of the same type, you can quickly\n identify a specific resource based on the tags you've assigned to it. For example, you can\n define a set of tags for your Amazon EMR on EKS clusters to help you track each\n cluster's owner and stack level. We recommend that you devise a consistent set of tag keys\n for each resource type. You can then search and filter the resources based on the tags that\n you add.
", "smithy.api#http": { "method": "POST", "uri": "/tags/{resourceArn}", @@ -4204,7 +4251,7 @@ } }, "traits": { - "smithy.api#documentation": "This entity describes a virtual cluster. A virtual cluster is a Kubernetes namespace\n that Amazon EMR is registered with. Amazon EMR uses virtual clusters to run jobs and host\n endpoints. Multiple virtual clusters can be backed by the same physical cluster. However,\n each virtual cluster maps to one namespace on an Amazon EKS cluster. Virtual clusters do not\n create any active resources that contribute to your bill or that require lifecycle\n management outside the service.
" + "smithy.api#documentation": "This entity describes a virtual cluster. A virtual cluster is a Kubernetes namespace\n that Amazon EMR is registered with. Amazon EMR uses virtual clusters to run\n jobs and host endpoints. Multiple virtual clusters can be backed by the same physical\n cluster. However, each virtual cluster maps to one namespace on an Amazon EKS\n cluster. Virtual clusters do not create any active resources that contribute to your bill\n or that require lifecycle management outside the service.
" } }, "com.amazonaws.emrcontainers#VirtualClusterArn": {