EMRContainers

Client

class EMRContainers.Client

A low-level client representing Amazon EMR Containers

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

• It is the prefix in the CLI commands for Amazon EMR on EKS. For example, aws emr-containers start-job-run.

• It is the prefix before IAM policy actions for Amazon EMR on EKS. For example, "Action": [ "emr-containers:StartJobRun"]. For more information, see Policy actions for Amazon EMR on EKS.

• It is the prefix used in Amazon EMR on EKS service endpoints. For example, emr-containers.us-east-2.amazonaws.com. For more information, see Amazon EMR on EKSService Endpoints.

import boto3

client = boto3.client('emr-containers')

These are the available methods:

• can_paginate
• cancel_job_run
• close
• create_job_template
• create_managed_endpoint
• create_virtual_cluster
• delete_job_template
• delete_managed_endpoint
• delete_virtual_cluster
• describe_job_run
• describe_job_template
• describe_managed_endpoint
• describe_virtual_cluster
• get_paginator
• get_waiter
• list_job_runs
• list_job_templates
• list_managed_endpoints
• list_tags_for_resource
• list_virtual_clusters
• start_job_run
• tag_resource
• untag_resource

Paginators

Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.

The available paginators are:

• ListJobRuns
• ListJobTemplates
• ListManagedEndpoints
• ListVirtualClusters