@aws-sdk/client-emr-containers 3.312.0 → 3.316.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist-cjs/EMRContainers.js +23 -266
- package/dist-cjs/protocols/Aws_restJson1.js +282 -665
- package/dist-es/EMRContainers.js +23 -266
- package/dist-es/protocols/Aws_restJson1.js +257 -640
- package/dist-types/EMRContainers.d.ts +49 -113
- package/dist-types/ts3.4/EMRContainers.d.ts +4 -1
- package/package.json +6 -6
|
@@ -19,212 +19,148 @@ import { StartJobRunCommandInput, StartJobRunCommandOutput } from "./commands/St
|
|
|
19
19
|
import { TagResourceCommandInput, TagResourceCommandOutput } from "./commands/TagResourceCommand";
|
|
20
20
|
import { UntagResourceCommandInput, UntagResourceCommandOutput } from "./commands/UntagResourceCommand";
|
|
21
21
|
import { EMRContainersClient } from "./EMRContainersClient";
|
|
22
|
-
|
|
23
|
-
* @public
|
|
24
|
-
* <p>Amazon EMR on EKS provides a deployment option for Amazon EMR that allows
|
|
25
|
-
* you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).
|
|
26
|
-
* 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.
|
|
27
|
-
* For more information about Amazon EMR on EKS concepts and tasks, see <a href="https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/emr-eks.html">What is
|
|
28
|
-
* shared id="EMR-EKS"/></a>.</p>
|
|
29
|
-
* <p>
|
|
30
|
-
* <i>Amazon EMR containers</i> is the API name for Amazon EMR on EKS.
|
|
31
|
-
* The <code>emr-containers</code> prefix is used in the following scenarios: </p>
|
|
32
|
-
* <ul>
|
|
33
|
-
* <li>
|
|
34
|
-
* <p>It is the prefix in the CLI commands for Amazon EMR on EKS. For example,
|
|
35
|
-
* <code>aws emr-containers start-job-run</code>.</p>
|
|
36
|
-
* </li>
|
|
37
|
-
* <li>
|
|
38
|
-
* <p>It is the prefix before IAM policy actions for Amazon EMR on EKS. For
|
|
39
|
-
* example, <code>"Action": [ "emr-containers:StartJobRun"]</code>. For more
|
|
40
|
-
* information, see <a href="https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies-actions">Policy actions for Amazon EMR on EKS</a>.</p>
|
|
41
|
-
* </li>
|
|
42
|
-
* <li>
|
|
43
|
-
* <p>It is the prefix used in Amazon EMR on EKS service endpoints. For example,
|
|
44
|
-
* <code>emr-containers.us-east-2.amazonaws.com</code>. For more information, see
|
|
45
|
-
* <a href="https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/service-quotas.html#service-endpoints">Amazon EMR on EKSService Endpoints</a>.</p>
|
|
46
|
-
* </li>
|
|
47
|
-
* </ul>
|
|
48
|
-
*/
|
|
49
|
-
export declare class EMRContainers extends EMRContainersClient {
|
|
22
|
+
export interface EMRContainers {
|
|
50
23
|
/**
|
|
51
|
-
* @
|
|
52
|
-
* <p>Cancels a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or
|
|
53
|
-
* SparkSQL query, that you submit to Amazon EMR on EKS.</p>
|
|
24
|
+
* @see {@link CancelJobRunCommand}
|
|
54
25
|
*/
|
|
55
26
|
cancelJobRun(args: CancelJobRunCommandInput, options?: __HttpHandlerOptions): Promise<CancelJobRunCommandOutput>;
|
|
56
27
|
cancelJobRun(args: CancelJobRunCommandInput, cb: (err: any, data?: CancelJobRunCommandOutput) => void): void;
|
|
57
28
|
cancelJobRun(args: CancelJobRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CancelJobRunCommandOutput) => void): void;
|
|
58
29
|
/**
|
|
59
|
-
* @
|
|
60
|
-
* <p>Creates a job template. Job template stores values of StartJobRun API request in a
|
|
61
|
-
* template and can be used to start a job run. Job template allows two use cases: avoid
|
|
62
|
-
* repeating recurring StartJobRun API request values, enforcing certain values in StartJobRun
|
|
63
|
-
* API request.</p>
|
|
30
|
+
* @see {@link CreateJobTemplateCommand}
|
|
64
31
|
*/
|
|
65
32
|
createJobTemplate(args: CreateJobTemplateCommandInput, options?: __HttpHandlerOptions): Promise<CreateJobTemplateCommandOutput>;
|
|
66
33
|
createJobTemplate(args: CreateJobTemplateCommandInput, cb: (err: any, data?: CreateJobTemplateCommandOutput) => void): void;
|
|
67
34
|
createJobTemplate(args: CreateJobTemplateCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateJobTemplateCommandOutput) => void): void;
|
|
68
35
|
/**
|
|
69
|
-
* @
|
|
70
|
-
* <p>Creates a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to
|
|
71
|
-
* Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual
|
|
72
|
-
* cluster.</p>
|
|
36
|
+
* @see {@link CreateManagedEndpointCommand}
|
|
73
37
|
*/
|
|
74
38
|
createManagedEndpoint(args: CreateManagedEndpointCommandInput, options?: __HttpHandlerOptions): Promise<CreateManagedEndpointCommandOutput>;
|
|
75
39
|
createManagedEndpoint(args: CreateManagedEndpointCommandInput, cb: (err: any, data?: CreateManagedEndpointCommandOutput) => void): void;
|
|
76
40
|
createManagedEndpoint(args: CreateManagedEndpointCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateManagedEndpointCommandOutput) => void): void;
|
|
77
41
|
/**
|
|
78
|
-
* @
|
|
79
|
-
* <p>Creates a virtual cluster. Virtual cluster is a managed entity on Amazon EMR on EKS. You can create, describe, list and delete virtual clusters. They do not consume any
|
|
80
|
-
* additional resource in your system. A single virtual cluster maps to a single Kubernetes
|
|
81
|
-
* namespace. Given this relationship, you can model virtual clusters the same way you model
|
|
82
|
-
* Kubernetes namespaces to meet your requirements.</p>
|
|
42
|
+
* @see {@link CreateVirtualClusterCommand}
|
|
83
43
|
*/
|
|
84
44
|
createVirtualCluster(args: CreateVirtualClusterCommandInput, options?: __HttpHandlerOptions): Promise<CreateVirtualClusterCommandOutput>;
|
|
85
45
|
createVirtualCluster(args: CreateVirtualClusterCommandInput, cb: (err: any, data?: CreateVirtualClusterCommandOutput) => void): void;
|
|
86
46
|
createVirtualCluster(args: CreateVirtualClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateVirtualClusterCommandOutput) => void): void;
|
|
87
47
|
/**
|
|
88
|
-
* @
|
|
89
|
-
* <p>Deletes a job template. Job template stores values of StartJobRun API request in a
|
|
90
|
-
* template and can be used to start a job run. Job template allows two use cases: avoid
|
|
91
|
-
* repeating recurring StartJobRun API request values, enforcing certain values in StartJobRun
|
|
92
|
-
* API request.</p>
|
|
48
|
+
* @see {@link DeleteJobTemplateCommand}
|
|
93
49
|
*/
|
|
94
50
|
deleteJobTemplate(args: DeleteJobTemplateCommandInput, options?: __HttpHandlerOptions): Promise<DeleteJobTemplateCommandOutput>;
|
|
95
51
|
deleteJobTemplate(args: DeleteJobTemplateCommandInput, cb: (err: any, data?: DeleteJobTemplateCommandOutput) => void): void;
|
|
96
52
|
deleteJobTemplate(args: DeleteJobTemplateCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteJobTemplateCommandOutput) => void): void;
|
|
97
53
|
/**
|
|
98
|
-
* @
|
|
99
|
-
* <p>Deletes a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to
|
|
100
|
-
* Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual
|
|
101
|
-
* cluster.</p>
|
|
54
|
+
* @see {@link DeleteManagedEndpointCommand}
|
|
102
55
|
*/
|
|
103
56
|
deleteManagedEndpoint(args: DeleteManagedEndpointCommandInput, options?: __HttpHandlerOptions): Promise<DeleteManagedEndpointCommandOutput>;
|
|
104
57
|
deleteManagedEndpoint(args: DeleteManagedEndpointCommandInput, cb: (err: any, data?: DeleteManagedEndpointCommandOutput) => void): void;
|
|
105
58
|
deleteManagedEndpoint(args: DeleteManagedEndpointCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteManagedEndpointCommandOutput) => void): void;
|
|
106
59
|
/**
|
|
107
|
-
* @
|
|
108
|
-
* <p>Deletes a virtual cluster. Virtual cluster is a managed entity on Amazon EMR on EKS. You can create, describe, list and delete virtual clusters. They do not consume any
|
|
109
|
-
* additional resource in your system. A single virtual cluster maps to a single Kubernetes
|
|
110
|
-
* namespace. Given this relationship, you can model virtual clusters the same way you model
|
|
111
|
-
* Kubernetes namespaces to meet your requirements.</p>
|
|
60
|
+
* @see {@link DeleteVirtualClusterCommand}
|
|
112
61
|
*/
|
|
113
62
|
deleteVirtualCluster(args: DeleteVirtualClusterCommandInput, options?: __HttpHandlerOptions): Promise<DeleteVirtualClusterCommandOutput>;
|
|
114
63
|
deleteVirtualCluster(args: DeleteVirtualClusterCommandInput, cb: (err: any, data?: DeleteVirtualClusterCommandOutput) => void): void;
|
|
115
64
|
deleteVirtualCluster(args: DeleteVirtualClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteVirtualClusterCommandOutput) => void): void;
|
|
116
65
|
/**
|
|
117
|
-
* @
|
|
118
|
-
* <p>Displays detailed information about a job run. A job run is a unit of work, such as a
|
|
119
|
-
* Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS.</p>
|
|
66
|
+
* @see {@link DescribeJobRunCommand}
|
|
120
67
|
*/
|
|
121
68
|
describeJobRun(args: DescribeJobRunCommandInput, options?: __HttpHandlerOptions): Promise<DescribeJobRunCommandOutput>;
|
|
122
69
|
describeJobRun(args: DescribeJobRunCommandInput, cb: (err: any, data?: DescribeJobRunCommandOutput) => void): void;
|
|
123
70
|
describeJobRun(args: DescribeJobRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeJobRunCommandOutput) => void): void;
|
|
124
71
|
/**
|
|
125
|
-
* @
|
|
126
|
-
* <p>Displays detailed information about a specified job template. Job template stores values
|
|
127
|
-
* of StartJobRun API request in a template and can be used to start a job run. Job template
|
|
128
|
-
* allows two use cases: avoid repeating recurring StartJobRun API request values, enforcing
|
|
129
|
-
* certain values in StartJobRun API request.</p>
|
|
72
|
+
* @see {@link DescribeJobTemplateCommand}
|
|
130
73
|
*/
|
|
131
74
|
describeJobTemplate(args: DescribeJobTemplateCommandInput, options?: __HttpHandlerOptions): Promise<DescribeJobTemplateCommandOutput>;
|
|
132
75
|
describeJobTemplate(args: DescribeJobTemplateCommandInput, cb: (err: any, data?: DescribeJobTemplateCommandOutput) => void): void;
|
|
133
76
|
describeJobTemplate(args: DescribeJobTemplateCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeJobTemplateCommandOutput) => void): void;
|
|
134
77
|
/**
|
|
135
|
-
* @
|
|
136
|
-
* <p>Displays detailed information about a managed endpoint. A managed endpoint is a gateway
|
|
137
|
-
* that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with
|
|
138
|
-
* your virtual cluster.</p>
|
|
78
|
+
* @see {@link DescribeManagedEndpointCommand}
|
|
139
79
|
*/
|
|
140
80
|
describeManagedEndpoint(args: DescribeManagedEndpointCommandInput, options?: __HttpHandlerOptions): Promise<DescribeManagedEndpointCommandOutput>;
|
|
141
81
|
describeManagedEndpoint(args: DescribeManagedEndpointCommandInput, cb: (err: any, data?: DescribeManagedEndpointCommandOutput) => void): void;
|
|
142
82
|
describeManagedEndpoint(args: DescribeManagedEndpointCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeManagedEndpointCommandOutput) => void): void;
|
|
143
83
|
/**
|
|
144
|
-
* @
|
|
145
|
-
* <p>Displays detailed information about a specified virtual cluster. Virtual cluster is a
|
|
146
|
-
* managed entity on Amazon EMR on EKS. You can create, describe, list and delete virtual
|
|
147
|
-
* clusters. They do not consume any additional resource in your system. A single virtual
|
|
148
|
-
* cluster maps to a single Kubernetes namespace. Given this relationship, you can model
|
|
149
|
-
* virtual clusters the same way you model Kubernetes namespaces to meet your
|
|
150
|
-
* requirements.</p>
|
|
84
|
+
* @see {@link DescribeVirtualClusterCommand}
|
|
151
85
|
*/
|
|
152
86
|
describeVirtualCluster(args: DescribeVirtualClusterCommandInput, options?: __HttpHandlerOptions): Promise<DescribeVirtualClusterCommandOutput>;
|
|
153
87
|
describeVirtualCluster(args: DescribeVirtualClusterCommandInput, cb: (err: any, data?: DescribeVirtualClusterCommandOutput) => void): void;
|
|
154
88
|
describeVirtualCluster(args: DescribeVirtualClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeVirtualClusterCommandOutput) => void): void;
|
|
155
89
|
/**
|
|
156
|
-
* @
|
|
157
|
-
* <p>Lists job runs based on a set of parameters. A job run is a unit of work, such as a
|
|
158
|
-
* Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS.</p>
|
|
90
|
+
* @see {@link ListJobRunsCommand}
|
|
159
91
|
*/
|
|
160
92
|
listJobRuns(args: ListJobRunsCommandInput, options?: __HttpHandlerOptions): Promise<ListJobRunsCommandOutput>;
|
|
161
93
|
listJobRuns(args: ListJobRunsCommandInput, cb: (err: any, data?: ListJobRunsCommandOutput) => void): void;
|
|
162
94
|
listJobRuns(args: ListJobRunsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListJobRunsCommandOutput) => void): void;
|
|
163
95
|
/**
|
|
164
|
-
* @
|
|
165
|
-
* <p>Lists job templates based on a set of parameters. Job template stores values of
|
|
166
|
-
* StartJobRun API request in a template and can be used to start a job run. Job template
|
|
167
|
-
* allows two use cases: avoid repeating recurring StartJobRun API request values, enforcing
|
|
168
|
-
* certain values in StartJobRun API request.</p>
|
|
96
|
+
* @see {@link ListJobTemplatesCommand}
|
|
169
97
|
*/
|
|
170
98
|
listJobTemplates(args: ListJobTemplatesCommandInput, options?: __HttpHandlerOptions): Promise<ListJobTemplatesCommandOutput>;
|
|
171
99
|
listJobTemplates(args: ListJobTemplatesCommandInput, cb: (err: any, data?: ListJobTemplatesCommandOutput) => void): void;
|
|
172
100
|
listJobTemplates(args: ListJobTemplatesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListJobTemplatesCommandOutput) => void): void;
|
|
173
101
|
/**
|
|
174
|
-
* @
|
|
175
|
-
* <p>Lists managed endpoints based on a set of parameters. A managed endpoint is a gateway
|
|
176
|
-
* that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with
|
|
177
|
-
* your virtual cluster.</p>
|
|
102
|
+
* @see {@link ListManagedEndpointsCommand}
|
|
178
103
|
*/
|
|
179
104
|
listManagedEndpoints(args: ListManagedEndpointsCommandInput, options?: __HttpHandlerOptions): Promise<ListManagedEndpointsCommandOutput>;
|
|
180
105
|
listManagedEndpoints(args: ListManagedEndpointsCommandInput, cb: (err: any, data?: ListManagedEndpointsCommandOutput) => void): void;
|
|
181
106
|
listManagedEndpoints(args: ListManagedEndpointsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListManagedEndpointsCommandOutput) => void): void;
|
|
182
107
|
/**
|
|
183
|
-
* @
|
|
184
|
-
* <p>Lists the tags assigned to the resources.</p>
|
|
108
|
+
* @see {@link ListTagsForResourceCommand}
|
|
185
109
|
*/
|
|
186
110
|
listTagsForResource(args: ListTagsForResourceCommandInput, options?: __HttpHandlerOptions): Promise<ListTagsForResourceCommandOutput>;
|
|
187
111
|
listTagsForResource(args: ListTagsForResourceCommandInput, cb: (err: any, data?: ListTagsForResourceCommandOutput) => void): void;
|
|
188
112
|
listTagsForResource(args: ListTagsForResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListTagsForResourceCommandOutput) => void): void;
|
|
189
113
|
/**
|
|
190
|
-
* @
|
|
191
|
-
* <p>Lists information about the specified virtual cluster. Virtual cluster is a managed
|
|
192
|
-
* entity on Amazon EMR on EKS. You can create, describe, list and delete virtual
|
|
193
|
-
* clusters. They do not consume any additional resource in your system. A single virtual
|
|
194
|
-
* cluster maps to a single Kubernetes namespace. Given this relationship, you can model
|
|
195
|
-
* virtual clusters the same way you model Kubernetes namespaces to meet your
|
|
196
|
-
* requirements.</p>
|
|
114
|
+
* @see {@link ListVirtualClustersCommand}
|
|
197
115
|
*/
|
|
198
116
|
listVirtualClusters(args: ListVirtualClustersCommandInput, options?: __HttpHandlerOptions): Promise<ListVirtualClustersCommandOutput>;
|
|
199
117
|
listVirtualClusters(args: ListVirtualClustersCommandInput, cb: (err: any, data?: ListVirtualClustersCommandOutput) => void): void;
|
|
200
118
|
listVirtualClusters(args: ListVirtualClustersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListVirtualClustersCommandOutput) => void): void;
|
|
201
119
|
/**
|
|
202
|
-
* @
|
|
203
|
-
* <p>Starts a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or
|
|
204
|
-
* SparkSQL query, that you submit to Amazon EMR on EKS.</p>
|
|
120
|
+
* @see {@link StartJobRunCommand}
|
|
205
121
|
*/
|
|
206
122
|
startJobRun(args: StartJobRunCommandInput, options?: __HttpHandlerOptions): Promise<StartJobRunCommandOutput>;
|
|
207
123
|
startJobRun(args: StartJobRunCommandInput, cb: (err: any, data?: StartJobRunCommandOutput) => void): void;
|
|
208
124
|
startJobRun(args: StartJobRunCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: StartJobRunCommandOutput) => void): void;
|
|
209
125
|
/**
|
|
210
|
-
* @
|
|
211
|
-
* <p>Assigns tags to resources. A tag is a label that you assign to an Amazon Web Services resource. Each tag
|
|
212
|
-
* consists of a key and an optional value, both of which you define. Tags enable you to
|
|
213
|
-
* categorize your Amazon Web Services resources by attributes such as purpose, owner, or environment. When
|
|
214
|
-
* you have many resources of the same type, you can quickly identify a specific resource
|
|
215
|
-
* based on the tags you've assigned to it. For example, you can define a set of tags for your
|
|
216
|
-
* Amazon EMR on EKS clusters to help you track each cluster's owner and stack level.
|
|
217
|
-
* We recommend that you devise a consistent set of tag keys for each resource type. You can
|
|
218
|
-
* then search and filter the resources based on the tags that you add.</p>
|
|
126
|
+
* @see {@link TagResourceCommand}
|
|
219
127
|
*/
|
|
220
128
|
tagResource(args: TagResourceCommandInput, options?: __HttpHandlerOptions): Promise<TagResourceCommandOutput>;
|
|
221
129
|
tagResource(args: TagResourceCommandInput, cb: (err: any, data?: TagResourceCommandOutput) => void): void;
|
|
222
130
|
tagResource(args: TagResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: TagResourceCommandOutput) => void): void;
|
|
223
131
|
/**
|
|
224
|
-
* @
|
|
225
|
-
* <p>Removes tags from resources.</p>
|
|
132
|
+
* @see {@link UntagResourceCommand}
|
|
226
133
|
*/
|
|
227
134
|
untagResource(args: UntagResourceCommandInput, options?: __HttpHandlerOptions): Promise<UntagResourceCommandOutput>;
|
|
228
135
|
untagResource(args: UntagResourceCommandInput, cb: (err: any, data?: UntagResourceCommandOutput) => void): void;
|
|
229
136
|
untagResource(args: UntagResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UntagResourceCommandOutput) => void): void;
|
|
230
137
|
}
|
|
138
|
+
/**
|
|
139
|
+
* @public
|
|
140
|
+
* <p>Amazon EMR on EKS provides a deployment option for Amazon EMR that allows
|
|
141
|
+
* you to run open-source big data frameworks on Amazon Elastic Kubernetes Service (Amazon EKS).
|
|
142
|
+
* 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.
|
|
143
|
+
* For more information about Amazon EMR on EKS concepts and tasks, see <a href="https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/emr-eks.html">What is
|
|
144
|
+
* shared id="EMR-EKS"/></a>.</p>
|
|
145
|
+
* <p>
|
|
146
|
+
* <i>Amazon EMR containers</i> is the API name for Amazon EMR on EKS.
|
|
147
|
+
* The <code>emr-containers</code> prefix is used in the following scenarios: </p>
|
|
148
|
+
* <ul>
|
|
149
|
+
* <li>
|
|
150
|
+
* <p>It is the prefix in the CLI commands for Amazon EMR on EKS. For example,
|
|
151
|
+
* <code>aws emr-containers start-job-run</code>.</p>
|
|
152
|
+
* </li>
|
|
153
|
+
* <li>
|
|
154
|
+
* <p>It is the prefix before IAM policy actions for Amazon EMR on EKS. For
|
|
155
|
+
* example, <code>"Action": [ "emr-containers:StartJobRun"]</code>. For more
|
|
156
|
+
* information, see <a href="https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies-actions">Policy actions for Amazon EMR on EKS</a>.</p>
|
|
157
|
+
* </li>
|
|
158
|
+
* <li>
|
|
159
|
+
* <p>It is the prefix used in Amazon EMR on EKS service endpoints. For example,
|
|
160
|
+
* <code>emr-containers.us-east-2.amazonaws.com</code>. For more information, see
|
|
161
|
+
* <a href="https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/service-quotas.html#service-endpoints">Amazon EMR on EKSService Endpoints</a>.</p>
|
|
162
|
+
* </li>
|
|
163
|
+
* </ul>
|
|
164
|
+
*/
|
|
165
|
+
export declare class EMRContainers extends EMRContainersClient implements EMRContainers {
|
|
166
|
+
}
|
|
@@ -76,7 +76,7 @@ import {
|
|
|
76
76
|
UntagResourceCommandOutput,
|
|
77
77
|
} from "./commands/UntagResourceCommand";
|
|
78
78
|
import { EMRContainersClient } from "./EMRContainersClient";
|
|
79
|
-
export
|
|
79
|
+
export interface EMRContainers {
|
|
80
80
|
cancelJobRun(
|
|
81
81
|
args: CancelJobRunCommandInput,
|
|
82
82
|
options?: __HttpHandlerOptions
|
|
@@ -325,3 +325,6 @@ export declare class EMRContainers extends EMRContainersClient {
|
|
|
325
325
|
cb: (err: any, data?: UntagResourceCommandOutput) => void
|
|
326
326
|
): void;
|
|
327
327
|
}
|
|
328
|
+
export declare class EMRContainers
|
|
329
|
+
extends EMRContainersClient
|
|
330
|
+
implements EMRContainers {}
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aws-sdk/client-emr-containers",
|
|
3
3
|
"description": "AWS SDK for JavaScript Emr Containers Client for Node.js, Browser and React Native",
|
|
4
|
-
"version": "3.
|
|
4
|
+
"version": "3.316.0",
|
|
5
5
|
"scripts": {
|
|
6
6
|
"build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
|
|
7
7
|
"build:cjs": "tsc -p tsconfig.cjs.json",
|
|
@@ -21,9 +21,9 @@
|
|
|
21
21
|
"dependencies": {
|
|
22
22
|
"@aws-crypto/sha256-browser": "3.0.0",
|
|
23
23
|
"@aws-crypto/sha256-js": "3.0.0",
|
|
24
|
-
"@aws-sdk/client-sts": "3.
|
|
24
|
+
"@aws-sdk/client-sts": "3.316.0",
|
|
25
25
|
"@aws-sdk/config-resolver": "3.310.0",
|
|
26
|
-
"@aws-sdk/credential-provider-node": "3.
|
|
26
|
+
"@aws-sdk/credential-provider-node": "3.316.0",
|
|
27
27
|
"@aws-sdk/fetch-http-handler": "3.310.0",
|
|
28
28
|
"@aws-sdk/hash-node": "3.310.0",
|
|
29
29
|
"@aws-sdk/invalid-dependency": "3.310.0",
|
|
@@ -40,14 +40,14 @@
|
|
|
40
40
|
"@aws-sdk/node-config-provider": "3.310.0",
|
|
41
41
|
"@aws-sdk/node-http-handler": "3.310.0",
|
|
42
42
|
"@aws-sdk/protocol-http": "3.310.0",
|
|
43
|
-
"@aws-sdk/smithy-client": "3.
|
|
43
|
+
"@aws-sdk/smithy-client": "3.316.0",
|
|
44
44
|
"@aws-sdk/types": "3.310.0",
|
|
45
45
|
"@aws-sdk/url-parser": "3.310.0",
|
|
46
46
|
"@aws-sdk/util-base64": "3.310.0",
|
|
47
47
|
"@aws-sdk/util-body-length-browser": "3.310.0",
|
|
48
48
|
"@aws-sdk/util-body-length-node": "3.310.0",
|
|
49
|
-
"@aws-sdk/util-defaults-mode-browser": "3.
|
|
50
|
-
"@aws-sdk/util-defaults-mode-node": "3.
|
|
49
|
+
"@aws-sdk/util-defaults-mode-browser": "3.316.0",
|
|
50
|
+
"@aws-sdk/util-defaults-mode-node": "3.316.0",
|
|
51
51
|
"@aws-sdk/util-endpoints": "3.310.0",
|
|
52
52
|
"@aws-sdk/util-retry": "3.310.0",
|
|
53
53
|
"@aws-sdk/util-user-agent-browser": "3.310.0",
|