API for Amazon Elastic Inference¶

ABAP Package	`/AWS1/API_EIN_IMPL`
ABAP SDK "TLA"	`EIN`
ABAP Interface	`/AWS1/IF_EIN`

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 Inference is EIN. 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 Elastic Inference 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¶

Elastic Inference public APIs.

February 15, 2023: Starting April 15, 2023, AWS will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service.

Using the SDK¶

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

Your variable go_ein is an instance of /AWS1/IF_EIN, and all of the operations in the Amazon Elastic Inference service are accessed by calling methods in /AWS1/IF_EIN.

API Operations¶

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

Factory Method¶

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

Creates an object of type /AWS1/IF_EIN.

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_EIN` `/AWS1/IF_EIN`¶

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

Configuring Programmatically¶

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

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

Paginators¶

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