API for Amazon EMR Containers¶

ABAP Package	`/AWS1/API_EMC_IMPL`
ABAP SDK "TLA"	`EMC`
ABAP Interface	`/AWS1/IF_EMC`

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for Amazon EMR Containers is EMC. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation¶

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the EMR containers module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service¶

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 Amazon EMR on 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.

Using the SDK¶

In your code, create a client using the SDK module for Amazon EMR Containers, which is created with factory method /AWS1/CL_EMC_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_emc)       = /aws1/cl_emc_factory=>create( go_session ).

Your variable go_emc is an instance of /AWS1/IF_EMC, and all of the operations in the Amazon EMR Containers service are accessed by calling methods in /AWS1/IF_EMC.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Amazon EMR Containers, see the Operation List.

Factory Method¶

`/AWS1/CL_EMC_FACTORY=>create( )`¶

Creates an object of type /AWS1/IF_EMC.

IMPORTING¶

Optional arguments:¶

`IV_PROTOCOL` `TYPE /AWS1/RT_PROTOCOL` `/AWS1/RT_PROTOCOL`¶

`IO_SESSION` `TYPE REF TO /AWS1/CL_RT_SESSION_BASE` `/AWS1/CL_RT_SESSION_BASE`¶

`IV_REGION` `TYPE /AWS1/RT_REGION_ID` `/AWS1/RT_REGION_ID`¶

`IV_CUSTOM_ENDPOINT` `TYPE /AWS1/RT_ENDPOINT` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`OO_CLIENT` `TYPE REF TO /AWS1/IF_EMC` `/AWS1/IF_EMC`¶

/AWS1/IF_EMC represents the ABAP client for the EMR containers service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically¶

DATA(lo_config) = DATA(go_emc)->get_config( ).

lo_config is a variable of type /AWS1/CL_EMC_CONFIG. See the documentation for /AWS1/CL_EMC_CONFIG for details on the settings that can be configured.

Paginators¶

Paginators for Amazon EMR Containers can be created via get_paginator() which returns a paginator object of type /AWS1/IF_EMC_PAGINATOR. The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using has_next() and get_next() methods.

Details about the paginator methods available for service Amazon EMR Containers can be found in interface /AWS1/IF_EMC_PAGINATOR.