API for Amazon Elastic Kubernetes Service¶

ABAP Package	`/AWS1/API_EKS_IMPL`
ABAP SDK "TLA"	`EKS`
ABAP Interface	`/AWS1/IF_EKS`

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 Elastic Kubernetes Service is EKS. 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 EKS 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 Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on Amazon Web Services without needing to setup or maintain your own Kubernetes control plane. Kubernetes is an open-source system for automating the deployment, scaling, and management of containerized applications.

Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use all the existing plugins and tooling from the Kubernetes community. Applications running on Amazon EKS are fully compatible with applications running on any standard Kubernetes environment, whether running in on-premises data centers or public clouds. This means that you can easily migrate any standard Kubernetes application to Amazon EKS without any code modification required.

Using the SDK¶

In your code, create a client using the SDK module for Amazon Elastic Kubernetes Service, which is created with factory method /AWS1/CL_EKS_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_eks)       = /aws1/cl_eks_factory=>create( go_session ).

Your variable go_eks is an instance of /AWS1/IF_EKS, and all of the operations in the Amazon Elastic Kubernetes Service service are accessed by calling methods in /AWS1/IF_EKS.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in Amazon Elastic Kubernetes Service, see the Operation List.

Factory Method¶

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

Creates an object of type /AWS1/IF_EKS.

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_EKS` `/AWS1/IF_EKS`¶

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

Configuring Programmatically¶

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

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

Waiters¶

Waiters for Implementation can be accessed via get_waiter() method followed by the waiter method to be called.

Details about the waiter methods available for service Implementation can be found in interface /AWS1/IF_EKS_WAITER.

Paginators¶

Paginators for Amazon Elastic Kubernetes Service can be created via get_paginator() which returns a paginator object of type /AWS1/IF_EKS_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 Elastic Kubernetes Service can be found in interface /AWS1/IF_EKS_PAGINATOR.