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

EMRcontainers

import { EMRcontainers } from "https://aws-api.deno.dev/v0.4/services/emrcontainers.ts?docs=full";
class EMRcontainers {
constructor(apiFactory: client.ApiFactory);
async cancelJobRun(params: CancelJobRunRequest, opts?: client.RequestOptions): Promise<CancelJobRunResponse>;
async createJobTemplate(params: CreateJobTemplateRequest, opts?: client.RequestOptions): Promise<CreateJobTemplateResponse>;
async createManagedEndpoint(params: CreateManagedEndpointRequest, opts?: client.RequestOptions): Promise<CreateManagedEndpointResponse>;
async createVirtualCluster(params: CreateVirtualClusterRequest, opts?: client.RequestOptions): Promise<CreateVirtualClusterResponse>;
async deleteJobTemplate(params: DeleteJobTemplateRequest, opts?: client.RequestOptions): Promise<DeleteJobTemplateResponse>;
async deleteManagedEndpoint(params: DeleteManagedEndpointRequest, opts?: client.RequestOptions): Promise<DeleteManagedEndpointResponse>;
async deleteVirtualCluster(params: DeleteVirtualClusterRequest, opts?: client.RequestOptions): Promise<DeleteVirtualClusterResponse>;
async describeJobRun(params: DescribeJobRunRequest, opts?: client.RequestOptions): Promise<DescribeJobRunResponse>;
async describeJobTemplate(params: DescribeJobTemplateRequest, opts?: client.RequestOptions): Promise<DescribeJobTemplateResponse>;
async describeManagedEndpoint(params: DescribeManagedEndpointRequest, opts?: client.RequestOptions): Promise<DescribeManagedEndpointResponse>;
async describeVirtualCluster(params: DescribeVirtualClusterRequest, opts?: client.RequestOptions): Promise<DescribeVirtualClusterResponse>;
async listJobRuns(params: ListJobRunsRequest, opts?: client.RequestOptions): Promise<ListJobRunsResponse>;
async listJobTemplates(params?: ListJobTemplatesRequest, opts?: client.RequestOptions): Promise<ListJobTemplatesResponse>;
async listManagedEndpoints(params: ListManagedEndpointsRequest, opts?: client.RequestOptions): Promise<ListManagedEndpointsResponse>;
async listTagsForResource(params: ListTagsForResourceRequest, opts?: client.RequestOptions): Promise<ListTagsForResourceResponse>;
async listVirtualClusters(params?: ListVirtualClustersRequest, opts?: client.RequestOptions): Promise<ListVirtualClustersResponse>;
async startJobRun(params: StartJobRunRequest, opts?: client.RequestOptions): Promise<StartJobRunResponse>;
async tagResource(params: TagResourceRequest, opts?: client.RequestOptions): Promise<void>;
async untagResource(params: UntagResourceRequest, opts?: client.RequestOptions): Promise<void>;
 
static ApiMetadata: client.ApiMetadata;
}

§Constructors

§
new EMRcontainers(apiFactory: client.ApiFactory)
[src]

§Methods

§

Cancels a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS.

§

Creates a job template. Job template stores values of StartJobRun API request in a template and can be used to start a job run. Job template allows two use cases: avoid repeating recurring StartJobRun API request values, enforcing certain values in StartJobRun API request.

§

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 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 additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements.

§

Deletes a job template. Job template stores values of StartJobRun API request in a template and can be used to start a job run. Job template allows two use cases: avoid repeating recurring StartJobRun API request values, enforcing certain values in StartJobRun API request.

§

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 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 additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements.

§

Displays detailed information about a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS.

§

Displays detailed information about a specified job template. Job template stores values of StartJobRun API request in a template and can be used to start a job run. Job template allows two use cases: avoid repeating recurring StartJobRun API request values, enforcing certain values in StartJobRun API request.

§

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.

§

Displays detailed information about a specified 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 additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements.

§

Lists job runs based on a set of parameters. A job run is a unit of work, such as a Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS.

§

Lists job templates based on a set of parameters. Job template stores values of StartJobRun API request in a template and can be used to start a job run. Job template allows two use cases: avoid repeating recurring StartJobRun API request values, enforcing certain values in StartJobRun API request.

§

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.

§

Lists the tags assigned to the resources.

§

Lists information about the specified 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 additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements.

§

Starts a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS.

§
tagResource(params: TagResourceRequest, opts?: client.RequestOptions): Promise<void>
[src]

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.

§
untagResource(params: UntagResourceRequest, opts?: client.RequestOptions): Promise<void>
[src]

Removes tags from resources.

§Static Properties